5 ms·
This seems...highly impractical for...90% of operations I'd be wanting to do with a DBMS. It kinda seems like a 'different way for different's sake' kinda solu
by lostgame 5y ago
This seems...highly impractical for...90% of operations I'd be wanting to do with a DBMS.
It kinda seems like a 'different way for different's sake' kinda solution? :/
I understand there must be a minority of operations that can benefit from this, but overall I can't imagine this being popular for most DB operations.
- vidarh 5y agoIt tend to include a large proportion of the large, expensive reporting queries your business people want to do. Whether or not those kinds of queries dominates for your system will depend greatly on your system. You also need to reach a certain scale before the choice (either way) will affect you enough to matter. But when you reach that scale it can be the difference between reporting queries taking seconds vs. hours in some cases. For some systems you'll end up wanting both, and stream updates from the transaction focused db (row oriented) into a separate reporting database that uses a column store.