5 ms·

I like these kinds of blog posts. Not because he's ditching mongo, I like the detail around his thought process because there's an over-abundance of articles ab

I like these kinds of blog posts. Not because he's ditching mongo, I like the detail around his thought process because there's an over-abundance of articles about "large company does X" but less of the hobbyist version of the same.

zulban 3y ago
Thanks :)
hot_gril 3y ago
Not gonna lie, seeing him ditch Mongo for Postgres then say "API calls generally take 8 ms now, not 150 ms" made me a little happy. Mongo can make sense, but it seems like he was thoroughly on the hype train for it rather than actually needing it.
- pachouli-please 3y ago
  In the article, he mentioned that working in JSON seemed natural and comfortable. So after checking to be sure mongo was fairly mature and commonly used, went with it. Sounds reasonable and not hype train driven
  - hot_gril 3y ago
    Postgres had good JSON support in 2019, and he later realized JSON wasn't actually needed. Hype train is what made MongoDB a default recommendation when it's really a more niche option.
    - hot_gril 3y ago
      (To be clear, I'm not saying the author was hyping up Mongo, just that the hype got to him.)
  - DaiPlusPlus 3y ago
    > he mentioned that working in JSON seemed natural and comfortable As opposed to?
  - dizhn 3y ago
    It sounds reasonable as one of the options to try.
- cyclotron3k 3y ago
  I've heard it said that the best no-sql database is Postgres
  - re-thc 3y ago
    i.e. the best no-sql is sql!
  - hot_gril 3y ago
    The real point of NoSQL is to enable horizontal scaling, which is probably irrelevant to the author's use case.
    - brimstedt 3y ago
      Id say the point of nosql is rather "the right tool for the job". You can use an SQL db engine as a kv-store, but you can probably make a more efficient kv-store if you do not have the SQL constraints. (Oth SQL engines are pretty efficient for lots of use cases these days) Another example where SQL may not be the right choice is time series or graph DBs.
      - hot_gril 3y ago
        Postgres might even be a more efficient KV store than Mongo, just not as scalable beyond a single machine.
cyclotron3k 3y ago
Agreed. I'd love to find out the source of the spikes and OOM events though
- zulban 3y ago
  Oh my goodness, me too.

zulban 3y ago

Thanks :)

hot_gril 3y ago

Not gonna lie, seeing him ditch Mongo for Postgres then say "API calls generally take 8 ms now, not 150 ms" made me a little happy. Mongo can make sense, but it seems like he was thoroughly on the hype train for it rather than actually needing it.

pachouli-please 3y ago
In the article, he mentioned that working in JSON seemed natural and comfortable. So after checking to be sure mongo was fairly mature and commonly used, went with it. Sounds reasonable and not hype train driven
- hot_gril 3y ago
  Postgres had good JSON support in 2019, and he later realized JSON wasn't actually needed. Hype train is what made MongoDB a default recommendation when it's really a more niche option.
  - hot_gril 3y ago
    (To be clear, I'm not saying the author was hyping up Mongo, just that the hype got to him.)
- DaiPlusPlus 3y ago
  > he mentioned that working in JSON seemed natural and comfortable As opposed to?
- dizhn 3y ago
  It sounds reasonable as one of the options to try.
cyclotron3k 3y ago
I've heard it said that the best no-sql database is Postgres
- re-thc 3y ago
  i.e. the best no-sql is sql!
- hot_gril 3y ago
  The real point of NoSQL is to enable horizontal scaling, which is probably irrelevant to the author's use case.
  - brimstedt 3y ago
    Id say the point of nosql is rather "the right tool for the job". You can use an SQL db engine as a kv-store, but you can probably make a more efficient kv-store if you do not have the SQL constraints. (Oth SQL engines are pretty efficient for lots of use cases these days) Another example where SQL may not be the right choice is time series or graph DBs.
    - hot_gril 3y ago
      Postgres might even be a more efficient KV store than Mongo, just not as scalable beyond a single machine.

cyclotron3k 3y ago

Agreed. I'd love to find out the source of the spikes and OOM events though

zulban 3y ago
Oh my goodness, me too.