Get the latest tech news
Why aren't we all serverless yet?
The median product engineer should reason about applications as composites ofhigh-level, functional Lego blocks where technical low-level details areinvisibl...
The general trend of software eating the world is a simpler and more reasonable explanation for that level of growth, especially with AI putting downwards pressure on the cost and cognitive overhead to generate small pieces of purpose-specific code (a sweet spot for serverless). The transition to microservices depended on providing a new stack of technical infrastructure to solve distributed systems problems that emerged as soon as communication between Lego blocks took place over the network instead of a motherboard (to wit: on-wire formats, latency, reliability, data integrity, service discovery, deployment, observability, troubleshooting, etc.). Migrate existing workloads that have well-scoped, self-contained logic, don’t need complex state management, have low to mid-level traffic and bursty profiles that fit well with cost / performance trade-offs of serverless (that paragraph serves as a prompt into your favourite LLM, which should spit out some combination of event-driven, background tasks, glue for lightweight orchestration, user authentication flows, etc.)
Or read this on Hacker News