The Solution Architect’s Guide to Serverless

For years I’ve been proud to say I build 100% serverless cloud applications. I wore it as a badge of honor that the software I designed could elastically scale at every tier and cost virtually nothing to run at small to medium scale. I used to introduce myself to people in tech as a serverless architect and make the best effort to build apps with Lambda, Step Functions, or direct integrations through API Gateway as the only form of compute. But I was wrong in my thinking. That’s not necessarily the ideal way to build software. The best way to build software is the one that solves the business problem with the lowest <a href="https://betterprogramming.pub/understanding-total-cost-of-ownership-of-serverless-and-container-applications-5bce571f6f5d" rel="noopener ugc nofollow" target="_blank">total cost of ownership</a>. Yes, serverless services are great, but let’s be honest — not every business has the budget to upskill its entire engineering staff. Nor do they have the appetite to refactor everything to be completely serverless, and that’s ok. I’m going to assume you’re here because you’re interested in incorporating some serverless components into your existing stateful applications. <h1>Setting the Record Straight</h1> First, we need to address some information floating around the internet about serverless services. I’ve had many conversations with people that are dismissive around the topic because they are misinformed, operate under false pretenses, or fundamentally don’t get the point of serverless. You may or may not have heard a few of these. <a href="https://betterprogramming.pub/the-solution-architects-guide-to-serverless-27af39ad57b">Click Here</a>