5 ms·
Nice analysis and write up. What's the reason for choosing PGSQL? Your workload appears ideal for a NOSQL DB like mongo
by mankash666 9y ago
Nice analysis and write up. What's the reason for choosing PGSQL? Your workload appears ideal for a NOSQL DB like mongo
- golergka 9y ago> Your workload appears ideal for a NOSQL DB like mongo Can you expand on that a little bit, please?
- ddorian43 9y agoThat is a good workload for column-stores. Mongodb is row-store (an inefficient one at that).
- mankash666 9y agoThe aim of the product is to display usage trends to it's customer, in real time. My understanding as a non CS, self taught programmer is that such workloads are better served by NoSql DB s. Yes, this comes with the lack of acid compliance, but spotting trends in real-time (apparently) don't require acid compliance. Please correct me if wrong as I'm getting down voted, which is rather amusing
- ddorian43 9y agoNosql is very big. Compare redis + cassandra + elasticsearch and you'll see. You have to look at: data-structures the db uses, query patterns, data-velocity, data-shape, etc etc. Basically how the db really works in a low level, to understand what is it good for. Current case they: have a lot of data, need a lot of compression (or low overhead as possible), need as much query-selectivity as possible (reading as few rows as possible for each query) that's why they have a unique case of selective indexes. Bonus: mongodb agg sucks. Seach online for comparison to pg or es agg.
- abraae 9y agoobligatory http://www.mongodb-is-web-scale.com/ http://www.mongodb-is-web-scale.com/