I have no idea how to interpret your comment. Do you mean just throw an ORM library into your code and never give another thought to persistence issues? At sc

I have no idea how to interpret your comment. Do you mean just throw an ORM library into your code and never give another thought to persistence issues? At scale, there will always be challenges with latency, through put, correctness, and cost of persisting and retrieving data that require considering the specifics of your persistence code. The service I’m describing handles abstracting these persistence concerns so other services can be more stateless and not deal with those issues.