This. We spent months rewriting to get away from RethinkDB and back to PostgreSQL.
-
-
-
Anything in particular that caused you to do this?
- Još 7 drugih odgovora
Novi razgovor -
-
-
I learned that the hard way in a startup I co-founded in the past, using a fancy document-based database for a job that any SQL system would have done perfectly well. I spent so much time replicating functionality I needed, and it was less performant than a well-tuned Postgres.
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I'm a shameless shill for redis, and I like using a schema-less db when you don't have a clear idea what the optimal data structures look like, but ... Writing my own indexing code is the worst. I might have been better off using MySQL, all things considered.
-
At a previous startup, we actually had a mongodb collection called “relationships” that was full of documents mapping ids to each other. Talk about re-engineering sql in nosql. What a waste.
- Još 4 druga odgovora
Novi razgovor -
-
-
Hmm interesting to hear more
@arvidkahl &@Mr_AMed. Been doubting long between SQL and MongoDB, went with Mongo for my current SaaS cause of scalability and flexibility. Have I picked the wrong option? -
I would not say you picked the wrong option. Every situation is different. In my case, the more I had to create relations between documents, the more difficult and complicated it became to manage. So I switched to Postgres and it’s running smoother.
- Još 6 drugih odgovora
Novi razgovor -
-
-
I’m starting to realize that Postgres is a great database when your application starts getting bigger. I already run into major issues with mongodb even before I’ve built something substantial
-
The moment I understood that i would need to write my own logic for joins (or keep embedding and syncing documents), I knew I made the wrong choice back then. It still worked, but it was so much more complicated than it needed to be.
Kraj razgovora
Novi razgovor -
-
-
You can even read my book (yeah that’s me self-advertising for the book I wrote and self-publish). It’s all about getting to the next level as an application developer using
#PostgreSQL :https://theartofpostgresql.com/ -
I like it :D A thing I have struggled with (and never really learned) was how to use pgBouncer and similar scaling-related issues. In the end, I didn't have to use it, but it was hard to find solid information on how to do that.
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.