Oh I agree here, my eyes also have seen terrible things. I think one of the major points im trying to make is the same basis as old school distributed communic

Oh I agree here, my eyes also have seen terrible things. I think one of the major points im trying to make is the same basis as old school distributed communication. Generate a Data Access Layer( https://en.wikipedia.org/wiki/Data_access_layer https://en.wikipedia.org/wiki/Data_access_layer ). That does not mean that you should be DB-centric, but DATA-Centric. If your stack is written in one language, create a lib, that will be the key in going forward. Application logic as a whole can be distributed throughout thousands of services but your DAL should be a common base. - at least for things that are in one database - Here you can use procs, views or queries depending on what you like, but once i hit a couple of million guid entries in a db, i can in fact sometimes strip seconds of queries by saving on the round trip. Especiall in ERP Apps that "need to have all the data allways". Dont convert everything to stored procs of course because then you are just as unflexible as having a microservice per entity. All in all, I don't believe databases are ever gonna go away and that dbas are still underrated, even though data is gold. As we have seen with machine learning, well defined data sets are the key to better models, meaning faster and quicker results.