My guess is that almost all programming jobs are in fields that produce no more data than a gb or two a month.
I'm happy to be proven wrong, but I would guess that there are far more companies making project management software, time tracking apps, invoicing software, etc. than there are facebooks, googles or reddits obsessively logging every user mouse twitch.
And that's data that's much better sitting in a nice, normal, relational database.
Yes, it definitely seems with market leadership comes big data. Seems to me big data is highly relevant. More relevant now than ever.
I.e., if you are generating reports, running aggregations over a large amount of data you definitely need some parallelism and Postgres isn't designed to handle these loads (certainly not petabytes). Even aggregating 100's of GB probably requires (or at least is more cost effective using) multiple machines.
Now Hadoop may not be a particularly efficient solution unless you need 100's of machines. But there is a limit to what a non-parallel single machine database can do. There are other solutions in-between.
And you really don't have to be twitter or google to handle significant amount of data these days. People are recording much more data in the hope of generating new insights and do need tools to process that data.
Aggregating 100s of GB isn't much of a problem for PG these days. Yes, you can be faster - obviously - but it works quite well. And the price for separate systems (duplicated infrastructure, duplicated data, out-of-sync systems, ...) is noticable as well.
But yea, for many petabytes of data you either have to go to an entirely different system, or use something like Citus.
Disclaimer: I work on PG, and I used to work for Citus. So I'm definitely biased.
But I honestly don't think hundreds of users each querying 100s of GBs is all that common.
Even Postgres got this right recently with the introduction of the BRIN index, which is a lot more lightweight.
Look at Netezza, Oracle Exadata, and (disclaimer: I work on this) SQream DB, which can absolutely handle hundreds of terabytes without too much fuss.
First, NLP based search can be executed on top of any engine (APIs are very handy), relational, kv, graph, filesystem .. so that part is totally irrelevant.
Assuming "big data" in this context is still relational data, then any of those systems would suffice, within their own particular tradeoffs and features.
If you're talking about taking some questions and getting graphs from them, ThoughtSpot does a good job.
https://adamdrake.com/command-line-tools-can-be-235x-faster-...
> if you want to search over big data, which should be a pretty common procedure these days
It's not a common procedure by any stretch because the vast majority of datasets aren't really "big".
I'm genuinely curious, if you want to search over big data, which should be a pretty common procedure these days, what alternatives are there to a distributed file system? A dfs seems very complex to me. And it is not clear too me what alternative system designs a dfs will outperform. Is a dfs the only solution to big data?
Relational DBs do break down at a certain scale. What system do you turn to next? Nosql? Will that scale infinitely? Will any system scale infinitely?