Hello, @DMehaffy can you please share why you said “First of all, good choice on making the switch to PostgreSQL”? As one of the solutions engineers, I’d really like to know why you feel this was a good choice over staying with MongoDB.
Another reason I’m interested is I have experience with SQL Server, MySQL and MongoDB. I’ve seen them all run well under high loads with relational data and I’ve seen them all perform terribly. Obviously setup and optimization had a lot to do with it in each case I’ve seen. I’ve been sticking with MongoDB for things I build from scratch as it’s been more forgiving for someone like me who is experienced but doesn’t consider myself a pro-database admin. Plus it’s allowed me to get better at handling MongoDB and solving related problems.
As you know, Strapi doesn’t have a process for handling schema migrations (referenced topic) that is my biggest fear for trying to use strapi with anything other than MongoDB (besides not having as much end to end SQL experience).
When working with Ruby on Rails apps, I had the migration feature with Active Record that helped tremendously with avoiding some problems. I’m about to start a project with a lot of relational data that I know how to make perform well with MongoDB (when building manually…not necessarily with Strapi) but I wanted to try PostgreSQL. I found your comment when searching for information about PostgreSQL and MongoDB in Strapi.
When i saw your comment, I wanted to get more information about why you felt moving from MongoDB to PostgreSQL was a good choice despite not knowing anything about mrwindmills database needs. Can you elaborate please? Is Strapis integration with MongoDB broken or not as first class as the other supported databases?
Note i’m not trying to trigger a religious debate. I just wanted to hear more of your thoughts on PostgreSQL over Mongodb with Strapi.