Blue/green deployment

Tech Optimizer
February 27, 2025
Standard support for Amazon Aurora PostgreSQL-Compatible Edition and Amazon RDS for PostgreSQL version 12 will end on February 28, 2025. The final update for PostgreSQL 12, version 12.22, was released on November 21, 2024. PostgreSQL follows an annual major version release cycle, supporting each version for five years post-release. Upgrading to newer major versions requires careful planning and testing to ensure application compatibility. New features in higher PostgreSQL versions include performance improvements, enhanced security, and new functionalities. Aurora PostgreSQL now supports AWS Graviton4 instances, which provide up to 40% performance improvement over Graviton3 instances. Recommended upgrades include moving to PostgreSQL 16 or newer, with options for in-place upgrades, blue/green deployments, and out-of-place upgrades. Amazon RDS Extended Support allows continued operation on a major version beyond the standard support end date, available at an additional cost. Extended Support for Aurora PostgreSQL 12.x and Amazon RDS for PostgreSQL 12.x will incur charges starting March 1, 2025, and will cease upon upgrading.
Tech Optimizer
February 22, 2025
Mindbody utilizes a cloud-based platform for the fitness and wellness industry, offering services such as client booking, scheduling, payments, marketing, and analytics. Their email marketing platform is built on an Aurora PostgreSQL cluster, currently at version 13.8, with a size of approximately 17 TB and a workload distribution of 80% reads and 20% writes. Mindbody faced scaling and performance challenges due to architectural limitations and increasing data demands, leading to all workloads being directed to the writer node. The average BufferCacheHitRatio was below 80%, indicating frequent disk access rather than cache hits, contributing to higher query latencies and I/O costs. To address these issues, Mindbody adopted Aurora Optimized Reads, which enhances caching capacity and improves latency and throughput for I/O-intensive workloads. Transitioning required upgrading the database cluster to version 14.9 or higher, and extensive testing was conducted in a proof-of-concept environment. The upgrade process involved a blue/green deployment strategy to minimize production disruption. After implementing Aurora Optimized Reads, Mindbody experienced significant performance improvements, including a 50% reduction in average daily CPU utilization and a 90% reduction in ReadIOPS. The AuroraOptimizedReadsCacheHitRatio indicated that 85% of read requests were served from the optimized cache. Cost analysis revealed a 23% reduction in monthly Aurora costs post-transition, with potential for further savings by downsizing instances.
Tech Optimizer
December 13, 2024
Amazon RDS introduced Blue/Green Deployments for PostgreSQL in October 2023 to facilitate major version upgrades with minimal downtime. This feature uses community logical replication for data replication between different PostgreSQL versions, but has limitations such as inability to replicate schema changes. Physical replication is now an option for RDS Blue/Green Deployments, addressing constraints of logical replication and benefiting minor version upgrades, schema changes, and storage adjustments. Physical replication is the default method for blue/green deployments unless a major version upgrade is specified, in which case logical replication is used. Key benefits of physical replication include broad engine version support, no dependency on static parameter configurations, scalability for multi-tenant databases, simplified storage adjustments, no constraints on DDL operations, faster switchover without sequence sync delays, and efficient handling of large objects. To implement physical replication, users should ensure their deployment does not require a major version upgrade and follow specific steps for creating a blue/green deployment. For PostgreSQL versions 15.3 and lower, blue/green deployments default to physical replication, as major version upgrades are not supported. Users can perform a major version upgrade by first creating a deployment with a minor version upgrade, enabling logical replication, and then executing the switchover.
Search