I think the people from serverless (and apex) are doing an amazing job evangelizing about the benefits of server-less infrastructures and they have amazing projects they should be quite proud of.
Than been said, I think both projects walk different paths in order to achieve similar goals.
What is different with other approaches?
* Isolation is one of the most important things for us. Each of the stages of your application are deployed into independent Cloudformation stacks.
* We don't stream commands to the AWS api. Every single of your resources are created using CF.
* We respect the tooling of each of the runtimes so javascript, java or python developers should not get exposed to software they are not use to.
* Convention over configuration. Perhaps this is because my background is the Python/Django ecosystem, but writing 200 lines configuration files in JSON feels completely wrong to me.
* Documentation documentation documentation: Again, perhaps I've been badly educated by the Django community, but documentation and examples are (for me) the most important thing a project like this should have. That's why gordon's documentation is quite complete (I would say) and we have more than 20 example project including integrations with Slack, Telegram, Twilio... and AWS services such as Kinesis, Dynamodb, Apigateway, S3, Cloudwatch Events, Cloudwatch Scheduled Events, etc...
I think is an amazing moment to be involved in the server-less community and we'll all benefit from a thriving ecosystem like this :D
Great work on this. We're actually moving in a similar direction at Serverless with full Cloudformation support in our current development branch for all the reasons you listed. Would love to chat sometime, email is in my account page.
FWIW, I've been using serverless the last couple of weeks and I find the request-response parameter mapping absolutely maddening.
Most of us have become used to frameworks like express for specifying our routes and manually specifying API gateway rules feels like a huge step backwards.
Messing with Gordon now, but I've messed with nearly every other serverless framework. If you're looking for something express-y then you might like claudia.js's ApiBuilder, but the underlying API Gateway is always the lowest common denominator so this just adds some prettiness on top. https://github.com/claudiajs/claudia
Why should someone prefer it over https://github.com/serverless/serverless? Could you please provide some differences or benefits?
Thanks for project, though, looks great!
I think the people from serverless (and apex) are doing an amazing job evangelizing about the benefits of server-less infrastructures and they have an amazing project they should be quite proud of.
Than been said, I think both projects walk different paths in order to achieve similar goals.
What is different with other approaches?
* Isolation is one of the most important things for us. Each of the stages of your application are deployed into independent Cloudformation stacks.
* We don't stream commands to the AWS api. Every single of your resources are created using CF.
* We respect the tooling of each of the runtimes so javascript, java or python developers should not get exposed to software they are not use to.
* Convention over configuration. Perhaps this is because my background is the Python/Django ecosystem, but writing 200 lines configuration files in JSON feels completely wrong to me.
* Documentation documentation documentation: Again, perhaps I've been badly educated by the Django community, but documentation and examples are (for me) the most important thing a project like this should have. That's why gordon's documentation is quite complete (I would say) and we have more than 20 example project including integrations with Slack, Telegram, Twilio... and AWS services such as Kinesis, Dynamodb, Apigateway, S3, Cloudwatch Events, Cloudwatch Scheduled Events, etc...
I think is an amazing moment to be involved in the server-less community and we'll all benefit from a thriving ecosystem like this :D
Don't want to hijack the thread (sorry) but I've been working for the last 10 months in a tool which might be of the interest of people reading this article.
This tool will be opensource in the following weeks, but at the moment is in closed beta. I'm looking for people interested in giving it a look. If you are interested, drop me an email to me[at]jorgebastida.com and I'll invite you to the repo.
tl;dr version: Dead simple Lambda+Kinesis+Dynamodb+S3+CloudWatch+Apigateway over Cloudformation with support for Python, Javascript, Java, Go etc... Lot's of examples including Telegram, Twilio, Slack... and quite extensive documentation (which I think is the key of adoption of a technology like this).
Contrary to the author, I think Bootstrap is not used enough! The value it adds to a company to have their own hand-craft version of a CSS grid is sub zero.
Streetlife is Britain's local social network. Our mission is to help neighbours to connect and build stronger, safer, friendlier communities. Today, over 1,000,000 people use Streetlife to exchange local news, events and recommendations, to make real-world connections and to get together to improve their neighbourhoods.
We're a small team of smart, driven and determined people, based in Covent Garden. Our meetings are informal, our fridge is always full of drinks and snacks, and we're out to change the world, one community at a time. We treat our employees like adults, and trust them to work in whatever way helps them to be most productive. There are no fixed office hours, timesheets, or managers watching the clock and you can take as much or as little time off for holidays as you want.
It's literally bragging. The story's provocative lead ends with the words "Here is my story." as though told by the student, about an organization from hell.
But it's not his story!
The author is actually the bad guy! The thing that makes the experience hell is...him. He's just being a jerk, for numerous reasons. I hope he has $1 million lying around to contribute to cern's recruitment budget, because that's what his behavior costs as words of stories like this get around.
Just read the comments here at HN. In what possible universe is a public blog post like this an appropriate reaction? The only one damaging CERN's reputation is this guy.
What would "the right thing" be exactly? Nor enforcing their own rules, eating the costs of a student fucking up (when they didn't have to) and gaining the enmity of a software vendor?
They probably *should( eat the costs. If your employee breaks your machinery, well, fire him and move on.
As someone who is hardly the student's best friend on this thread, I'm skeptical they could really stick him with the 30K bill, and even more skeptical that they could get any of it from him, since he is judgment-proof.
