In my opinion (to summarize) this solve one of the main problem introduced by (wrongly implementing your microservices/ splitting your monolith) which is data intrgrity there is a reason why many cloud services are "eventually consitent" (no wonder the head quartes for such are located in such leftiest cities since its obvious they like the word-playing. By adding any modifier to "consistent" they are telling you it is NOT consitent, even if that is for a "brief" period of time).With this aproach you centralize your data and implement multiple actors working atop the same set of data; as they say in the article this comes to its own costs, mainly due to the limitations of existing ORM's (see https://blogs.tedneward.com/post/the-vietnam-of-computer-sci... you can jum onto "vietnam and OR mapping" to save you a bunch of historic bull crap) where then you have multiple applications working on the same set of data you go onto a more horrible place than data integrity issues, which is data corruption issues... In brief, choose your own poison, you like debugging the DB/data issues, debugging your apps, or having an un scalable system?