A blog post drawing a parallel between the application monolith era and today's database layer challenges. Just as microservices solved the problem of tightly coupled application code, the database connection layer remains a hidden monolith: when a breaking change is needed in the DB, every microservice must be updated simultaneously, negating the agility microservices promised. The post argues the microservices revolution is incomplete because it never truly reached the database layer, teasing a future solution.
Table of contents
Database monolithThe way we used to build applications…Microservices revolutionIs the revolution done? Or there’s still work to do?Sort: