> Sometimes a big old RDBMS housing all of your data which is actually already related in reality makes the most sense. Which is all fun and games until some i

> Sometimes a big old RDBMS housing all of your data which is actually already related in reality makes the most sense. Which is all fun and games until some intern gets asked to add a 'most popular' sort to the search page. He quickly figures out where the 'OrderProduct' table is, throws in a quick count and a group-by to the search query and the whole site gets taken down by it. Of course I take your point but there is somewhere between everything in one monolithic DB and every bit of data has its own microservice. It needs good judgement to divide it appropriately.