PGDay Lowlands2025

As with any love story, our journey with MongoDB took us through different stages of affection before we ultimately chose the best match for our needs. Mongo was our initial crush. Its attractive, JSON-like documents made it super easy and intuitive for developers to get started, which was a huge advantage. The schema-less design allowed us to avoid committing to a rigid structure upfront, and we fell for the freedom it offered being able to insert whatever we wanted, whenever we wanted.

However, after seven years of infatuation, this freedom began to create issues. Our prototypes never truly ended, often evolving into end-user applications. Data duplication led to consistency problems, and the schema of certain collections became chaotic: nested lists and objects slowed down performance, as there was no strict control over the data schema across different teams. As we started to outgrow our initial fascination with Mongo, we started looking for a more reliable option to meet our evolving requirements.

That's when we met Postgres. With its ability to maintain data consistency through foreign keys, enforce a controlled schema and allowing insert new functionality throw extensions made Postgres became the partner we needed Thanks to this, we now have more trust in our data and faster queries, solidifying our commitment to a stable, long-term relationship.