What is the future of RDBMS?

by · Published · Updated

       
alt

Serverless philosophy came a long way & likely to be the default architecture paradigm of the future. Currently, there are heavy uses of “serverless” for websites, applications, APIs, workflows & CDNs. In contrast, serverless RDBMSs are still not so widely used. While there are offerings like AWS Aurora (for MySQL), there are concerns in terms of security, access control, transaction mgmt, etc. As a result, RDBMSs still mostly get deployed either as on-prem or in VPC private subnets. But such deployments fail to align well with serverless apps & front-ends?

Should then lambda functions with infinite scalability be allowed to directly access RDBMS in provisioned environments with limited scalability? But that causes hotspots/bottlenecks!

Should we then wrap that DB with API to manage connections? But that increases latency?

It looks like serverless RDBMS is the answer that is further bolstered by “JAMstack” approach to modern web development with heavy caching of static pages in serverless CDN edges. Serverless databases would greatly augment this idea with high scalability & availability at these edges. That would be the architecture of the future.

Benefits are many – performance, security, faster development, costs & more.

Learn more about this in the article below.

Suvo Dutta

I have over 22 years of IT experience in strategy, advisory, innovations, and cloud-based solutions in the Insurance domain. I advise clients in transforming their IT ecosystems to future-ready architectures that can provide exemplary customer experience, improve operating efficiency, enable faster product development and unlock the power of data.

You may also like...