Serverless computing, a concept that has started gaining traction in the last two years, is all about shifting focus to applications that require no infrastructure management and consume resources only for the seconds for which they are active. In the public cloud space, serverless usually translates to solutions where the provider dynamically manages the allocation of server resources based on workload requirements.
AWS Lambda led the way, with Microsoft Azure Functions (and others) quickly catching up. Pricing for serverless frameworks is generally based on the actual amount of resources consumed by the application, instead of prepurchased capacity. As these serverless solutions for stateless applications gain popularity and adoption in next-generation software architectures, where does that leave the relational database? Still a crucial component for many, if not most, applications.
