Category: Best Practices

When getting started with DynamoDB, one of the first decisions you will make is choosing between two throughput modes: on-demand and provisioned. On-demand mode is the default and recommended throughput option because it simplifies building modern, serverless applications that can start small and scale to millions of requests per second. However, choosing the right throughput strategy requires evaluating your operational needs, development velocity, and application characteristics, with cost being a key consideration. In this post, we examine both throughput modes in detail, exploring their characteristics, strengths, and ideal use cases.

When you decide to upgrade your PostgreSQL database which is configured as source or target for an ongoing AWS DMS task, it’s important to factor this into your upgrade planning. In this post, we discuss the best practices to handle the AWS DMS tasks during PostgreSQL upgrades to minor or major versions.

In this post, we highlight often overlooked architectural designs and the inherent features of Aurora that optimize costs when deploying an open source database. The following sections examine various use cases, contrasting typical self-managed database configurations and their associated costs with the equivalent solution on Aurora, highlighting potential cost savings and operational efficiencies.

In this post, we show you a worked example of taking an existing application that works on PostgreSQL databases and adapting it to work with an Aurora DSQL database. In addition to adapting for the previously mentioned aspects, we also address some data type incompatibilities and work around some limits that currently exist in Aurora DSQL.

In this post, we dive into the various architecture patterns and options available for both compute and storage layers while configuring your self-managed Oracle databases on HAQM EC2 to comply with your HA and DR requirements.

In this post, we examine the realities behind common myths about DynamoDB on-demand capacity mode across three key areas: cost implications and efficiency, operational overhead and management, and performance considerations. We provide practical guidance to help you make informed decisions about throughput management.

In this post, we show you several long-term data backup strategies and how to effectively implement them in the AWS environment, with a focus on HAQM Relational Database Service (HAQM RDS) and HAQM Aurora.

In this post, we explore the end-of-life (EOL) timeline for Aurora PostgreSQL and HAQM RDS for PostgreSQL. We discuss features in PostgreSQL major versions, HAQM RDS Extended Support, and various upgrade strategies, including in-place upgrades, HAQM RDS blue/green deployments, and out-of-place upgrades.

Oracle Multitenant feature is available in Oracle database from 12cR1 (12.1.0.1) and later. This enables customers to use multiple PDBs in a single Oracle database, facilitating better manageability and consolidation of environments. In Oracle Multitenant architecture, there are various user management approaches available that can be used to create and manage user accounts in the container database (CDB) and PDBs. In this post we discuss the options for managing users and how they can be set up and used for different scenarios.

On October 22, 2024, we announced the availability of the Aurora Global Database writer endpoint, a highly available and fully managed endpoint for your global database that Aurora automatically updates to point to the current writer instance in your global cluster after a cross-Region switchover or failover, alleviating the need for application changes and simplifying routing requests to the writer instance. In this post, we dive deep into the new Global Database writer endpoint, covering its benefits and key considerations for using it with your applications.