| In my experience, it's always come down to either using a specific database type for the wrong job, or using a database type the wrong way. - Treating an OLAP like an OLTP. - Using a document store for relational data bc managing relations in SQL is tedious and slows development/progress/features. - Using OLTP for analytics. - and so on... And the usual reaction ensues. Conversations begin about migrating to another product while not really paying attention to interaction patterns and the intent/reason for the various workloads. Of course such migrations only lead to either... - Place-shifting the issues, or - Resolving the issues that lead to the migration while creating new ones that didn't exist before. Workloads that were suited to the existing DB are now mismatched to the new one. However, Postgres seems to be a pretty safe bet when such migrations are undertaken due to how versatile it is. Personally, I don't care which database is used (within reason of course). Just use the right database type for the job. |