4 ms·
Recently did this as MySQL was just not handling large tables as well we needed and their new partitioning and clustering were lackluster for our purposes. Wit
by xs83 7y ago
Recently did this as MySQL was just not handling large tables as well we needed and their new partitioning and clustering were lackluster for our purposes.
Without even implementing the partitioning and clustering - simply moving to Postgres has "reset" our performance problems on our system. We have tables with 10M+ rows in them that dragged on MySQL (Aurora RDS) - with Postgres (Aurora Postgres) things are running smoothly.
If you are dealing with huge amounts of data but not quite into "BigData" territory - I say go for it.
I just hope you have used an ORM or your queries are generalist enough to make the switch easy - even with an ORM it was a painful migration for us!