3 ms·
You have basically recreated your own datastore on top of an existing DBMS, on top of which you have to create your own database. You will have to translate que
by remram 4y ago
You have basically recreated your own datastore on top of an existing DBMS, on top of which you have to create your own database. You will have to translate queries and reimplement many features like schema/data migrations, constraints, ... to get to a similar product with worse performance but (hopefully) better suited for your deployment strategy.
Do what works for you I guess.
- stevenjgarner 4y agoFor sure. Performance has not been anywhere near as big a challenge as my own productivity. This EAV approach has enabled me to do at least more than an order of magnitude more solutions for customers in the same time. I basically manage 2 EAV databases - a production one with the 7 tables (discussed) and a development one with the same 7 tables, where I will do imports, migrations, and such. One thing that is truly chaos is when you have hundreds of "virtual" EAV tables with 10's of millions of records (or more) in just 7 tables .... and the house of cards comes down for whatever reason (master-master replication failure, clustering failure etc). Gives you a whole new appreciation of the beauty of a simple flat file database.