Are We Making Lambda Too Hard?

You may or may not know that <a href="https://readysetcloud.io/newsletter" rel="noopener ugc nofollow" target="_blank">I run a weekly serverless newsletter</a>. The newsletter compiles the best serverless content every week and gives a summary with my thoughts. I love doing it — it’s a great way to stay up to date on all the new feature releases and keep up with trending topics. While I won’t claim I read all content around serverless, I will claim that I read the majority of it. This has given me a pretty good indication of what people are doing at their jobs, how they are set up, and what people are pushing as best practices nowadays. I’m beginning to see a trend that I’m not sure I like… yet. There have been quite a few posts lately about how people recommend structuring Lambda-heavy projects. They talk about the different layers of code, responsibility separation, and code reusability. While these things might sound like no-brainers, it’s beginning to make Lambda development feel a bit complex and bring in some habits that seem to fight against the modularity and simplicity the service provides. <a href="https://betterprogramming.pub/are-we-making-lambda-too-hard-4008572ac63a">Learn More</a>