←back to thread

Analyzing database trends through 1.8M Hacker News headlines

(camelai.com)
171 points vercantez | 2 comments | 08 Jul 25 02:55 UTC | HN request time: 0.568s | source
Show context
nsbk ◴[10 Jul 25 15:57 UTC] No.44522431[source]▶
Some of the insights match my personal experience and preferences. At $dayjob we're migrating from Mongo to TimescaleDB (now TigerData ¯\_(ツ)_/¯) which is basically a PostgreSQL extension for time series data and couldn't be happier. We are getting better performance and massive storage savings.

On the analytics side of things we are starting to use DuckDB for some development efforts, but we are keen on potentially replacing some or all of our Snowflake usage with DuckDB.

replies(1): >>44522652 #
throw_m239339 ◴[10 Jul 25 16:18 UTC] No.44522652[source]▶
Can you tell me, the scenarios you used MongoDB for? Because I'm still curious about why would anyone use MongoDB after all these years.
replies(2): >>44522769 #>>44529369 #
1. nsbk ◴[10 Jul 25 16:29 UTC] No.44522769[source]▶
It is the main database for a huge Rails app. They adopted Mongo right when its popularity started to decline. I always thought it was a very poor choice since the day I joined.

It is a especially bad choice considering that a lot of the data stored in it is IoT-like and the system creates a single document per event :facepalm:

replies(1): >>44523868 #
2. beembeem ◴[10 Jul 25 18:11 UTC] No.44523868[source]▶
I'm sorry to hear about your bad experience. From your comment I take it that you weren't using a time-series collection to store data in mdb which uses industry-standard compression techniques?