News for hackers. Stuff that matters.

A comment on Summarizing Data in SQL. Parent comment

Re:Summarizing Data in SQL by evook on Sunday February 07, 2016 @04:36AM (#11052316)
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.

[ Parent | on HN ]
Re:Summarizing Data in SQL by jmsmistral on Sunday February 07, 2016 @06:12AM (#11052518)
I 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/

[ Parent | on HN ]