3 ms·
So does it kinda depend on what sort of searching you want to do? I'm currently trying to decide between ES and PostgreSQL. As I have read replica's for PG and
by philliphaydon 5y ago
So does it kinda depend on what sort of searching you want to do?
I'm currently trying to decide between ES and PostgreSQL. As I have read replica's for PG and the plan is to flatten the data into a single table, there's only ~4 fields that are text betwee 1-256 in length. While the other ~30 fields are int/decimal/date fields. There's prob ~8m records roughly that grows by 2-3m / year. So I feel like ES might be overkill for this and PG would be totally fine.
- mistrial9 5y agoone lense for the decision -- look at the rate of change of your dataset, and how important is total throughput.. if your dataset does not change very much, or changes at defined times in predictable ways, then I would say Postgres is a fine choice and your biggest problem will be defending against uninformed colleagues. Many small parts of Postgres are well thought out, and the manual has improved steadily over two decades.
- philliphaydon 5y agoNew data has a few fields which could change a lot within the first few hours but after that the data is more or less set and never changes. I love the PostgreSQL documentation!
- whitepoplar 5y agoYou may want to check out the ZomboDB Postgres extension!