3 ms·
Every database I could think of at the moment. Even SQL-Lite is able to handle billions of rows. Probably some xargs sed awk hacks are also sufficient for resu
by evook 11y ago
Every database I could think of at the moment. Even SQL-Lite is able to handle billions of rows.
Probably some xargs sed awk hacks are also sufficient for results in milliseconds.
You start getting problems when dealing with >128 TB databases like the legacy crm databases at Bayer and Siemens e.g.
- jmsmistral 11y agoI think ">128TB" is stretching the upper-limit for single-node database. When you're dealing with > 10TB in a single node, it's probably wise to 'shard' or partition the data over more than one node (think backups/archiving, query performance,...). To answer the initial question - take a look at CitusDB that runs over PostgreSQL. They seem to be doing some cool work in real-time analytics/scalability: https://www.citusdata.com/ https://www.citusdata.com/