The open source Serverless Framework is backed by a super smart and extensive community of developers (we've passed 17,000 stars on GitHub). Besides contributing code, our community is passionate about sharing their knowledge and expertise. Here's a roundup of some of these articles, videos, and posts to help you keep up with the news in the serverless ecosystem.
A look at microservices, not as a tool to scale the organization, development and release process (even though it's one of the main reasons for adopting microservices), but from an architecture and design perspective, and put it in its true context: distributed systems. In particular, we will discuss how to leverage Events-first Domain Driven Design and Reactive principles to build scalable microservices, working our way through the evolution of a scalable microservices-based system. - By Jonas Bonér
I ended up with a mess that cost more money than I wanted it to. It wasn't easy to figure out ... I had better luck with Firebase. I had a fun time and built something interesting. At least I think it is. I had to approach the development process in a completely different way than what I was used to... but I like that kind of thing. I know others don't. The big thing to me, however, is that I was able to build something that I would truly use. In fact I'm using parts of it now in production (more on that in a future post). - By Rob Conery
When I joined Postlight as an engineer last year, my first task was a big one: Rewrite the Readability Parser API ... ... Finally, we focused on cost, and the answer here was simple. To drastically reduce our costs, we chose a serverless architecture running on AWS Lambda and API Gateway, built and deployed using the Serverless framework. - By Adam Pash
Changing a functions dependent resources after deployment is a critical step towards feature parity with traditional architectures. When we talk about serverless architectures, we often talk about the natural fit between serverless and microservices. We’re already partitioning code into individually-deployed functions — and the current focus on RPC-based microservices will eventually change into event-driven microservices as serverless-native architectures become more mature. - By Ben Kehoe
This isn’t a tutorial, just a conceptual framework that’s helped me write better IAM policies. It’s extra useful when an app needs a group of services like DynamoDB, S3, and Kinesis. The method is called “CARE,” and it’s an acronym based on the four parts of an IAM policy statement. - By Ryan Scott Brown