Backend Functions
Decentrelon Backend Flow

Moving from MariaDb to PostgreSQL

Initially, the assumed requirement was ~10-15M data points and we just opted MySQL Because why not? Throw in some good indexes whatever you use for searching and joining. Voila! MySQL can easily handle 15M records. It can actually handle a lot more. However, the performance of MySQL decreases as the requirement for concurrency increases. PostgreSQL performs better relative to MySQL in case of higher concurrency and write/read ratios, albeit it has slower general reads than MySQL.

Amazon RDS PostgreSQL vs Aurora PostgreSQL

Amazon RDS for PostgreSQL and Aurora PostgreSQL are fully managed open-source PostgreSQL database services. They both offer provisioning various types of database instances, multiple PostgreSQL versions, managing backups, point-in-time recovery (PITR), replication, monitoring, Multi-AZ support, and Storage Auto Scaling.
Amazon RDS for PostgreSQL supports up to 64 TiB of storage and recent PostgreSQL versions.
DB instances for Amazon RDS for PostgreSQL use Amazon Elastic Block Store (Amazon EBS) volumes for database and log storage.
Aurora PostgreSQL uses a high-performance storage subsystem customized to take advantage of fast distributed storage. The underlying storage grows automatically in chunks of 10 GiB, up to 128 TiB. Aurora improves upon PostgreSQL for massive throughput and highly concurrent workloads. The combination of PostgreSQL compatibility with Aurora enterprise database capabilities provides an ideal target for commercial database migrations.
Aurora is a better choice given the requirement of high throughput and availability.
Export as PDF
Copy link
On this page
Moving from MariaDb to PostgreSQL
Amazon RDS PostgreSQL vs Aurora PostgreSQL