Hacker News Reader

If I were to start a new project, I would directly use postgres, and possibly add a JSONB column ONLY FOR OPTIONAL fields that you don't query frequently. Throwing everything in a document is just fermenting chaos and pain. That being said, I do love the syntax and structure of Mongo pipelines over SQL.

View on HN

At $WORK, we use the same approach for integrations with 3rd party systems.

The data that is common for all integrations are stored as columns in a relational table. Data that are specific for each integration are stored in JSONB. This is typically meta data used to manage each integration that varies.

It works great and you get the combination of relational safety and no-schema flexibility where it matters.

"Throwing everything in a document is just fermenting chaos and pain." - I LOVE THIS.

Reply on news.ycombinator.com