Why we're leaving serverless

So-called “server-less” environments necessarily require stitching services together, and that introduces latency. Single-machine monoliths will always be the fastest architecture. /p

https://unkey.com/serverless-exit

• The fundamental issue was caching. In serverless, you have no guaranteed persistent memory between function invocations. Every cache read requires a network request to an external store, and that’s where things got painful.

• here’s the thing: zero network requests are always faster than one network request

• you end up needing multiple other products to solve artificial problems that serverless itself created

• We found ourselves constantly evaluating and integrating new SaaS products, not to add business value, but just to work around the constraints of our chosen architecture.

• Working around statelessness creates complexity

• Sometimes the best solution isn’t to work around limitations but to choose a different foundation.