4 ms·

We went really deep on this recently, as we looked to migrate off Keen.io for that exact reason (only time based queries, also it's really slow). We didn't loo

We went really deep on this recently, as we looked to migrate off Keen.io for that exact reason (only time based queries, also it's really slow). We didn't look at MongoDB due to too many people on the team having been burned by it in the past, but after looking at a lot of stuff we settled on Redshift with a Postgres database in front of it using dblink and foreign data wrapper. This allowed us to have extremely fast reads of common queries with only a 5 minute lag on data becoming available. It's amazing what you can build with Postgres. I might write up a blog post about our exact strategy if that would be interesting to people.

gshulegaard 8y ago
+1 for me thinking that would be interesting. It wouldn't be something completely new for me, but I still think it would be interesting. I am also sure people not very familiar with Postgres would find even greater value in a post like that.
scottshamus 8y ago
Please do. It would be great to hear how a company took a pragmatic approach that worked well enough for them. The mindshare right now seems like people are pushing for using combination of five different technologies to do simple aggregation queries. Sometimes knowing a single tool really well is all you need...