Relational Tables & SQL should be just one storage mechanism for your app. What if someone told you: build an app, but only use b-trees? Then you start complai

Relational Tables & SQL should be just one storage mechanism for your app. What if someone told you: build an app, but only use b-trees? Then you start complaining about all the shortcomings of b-trees. The point is that you have relational tables / SQL, along with many other persistence , storage & indexing mechanisms: distributed hashtables, queues, lists, etc. All the apps I've worked on have mixed SQL with all of the other data structures with consistent or inconsistent replication among them depending on the use-case. One way to manage this is a key-value online tier and a relational offline tier, with inconsistent replication online to offline. SQL & RDMBS are very powerful, but like any tool, limited to the designated use case. Stop trying to make it do everything.