DATABASE INTELLIGENCE CENTER
Each database view separates current release posture, security evidence, engineering checks, and vendor-published production use cases. Progress is stored only in this browser.
CLOUD BLUEPRINT
Treat Aurora PostgreSQL as a managed AWS database platform: validate architecture, failover behavior, performance, upgrades, backup/recovery, observability, and migration patterns.
EVIDENCE SNAPSHOT · VERIFIED 05 SEP 2026
Published versions can vary by AWS Region. Validate the exact engine version before planning an upgrade.
Compatibility is tested before data movement. Cutover occurs only after data, query, performance, and rollback evidence is complete.
ENGINEERING · COST REFERENCE · VERIFIED 05 SEP 2026
Public pricing references are shown only where the source supports them. Database count alone does not determine Processor, PVU, vCPU, instance, storage, I/O, replica, or cluster quantities.
Database count alone is not the licensing or infrastructure quantity. Each benchmark below states the unit being multiplied—PVU, Processor, vCPU, instance configuration, or cluster—so the reference stays comparable without presenting it as an estate quote.
| Platform | Verified public reference | 100-unit reference benchmark | What is actually known |
|---|---|---|---|
| IBM Db2 12.1 AESERELATIONAL · ON-PREM |
IBM: AESE 12.1 uses PVU.
SHI current selling price: $1,805 / PVU
SHI also lists MSRP $1,509 / PVU. The page is a current AESE 1-PVU reseller listing and is marked EOL by SHI; it does not state Db2 12.1. IBM separately confirms that AESE remains available in Db2 12.1 under the PVU metric.
|
100-PVU benchmark:SHI selling price: $180,500 SHI-listed MSRP: $150,900 |
Db2 12.1 AESE uses PVU licensing. The dollar benchmark is from SHI, not an IBM contract quote; actual estate cost depends on licensed PVU quantity. |
| Oracle Database EERELATIONAL · ON-PREM |
EE: $47,500 / Processor
RAC: +$23,000 / Processor
GoldenGate: $17,500 / Processor
Active Data Guard: +$11,500 / Processor
Oracle Technology Global Price List dated August 3, 2026. GoldenGate licensing includes Active Data Guard rights; do not add the ADG option again when GoldenGate is licensed.
|
100-Processor benchmarks:EE: $4.75M EE + RAC: $7.05M EE + Active Data Guard: $5.90M EE + GoldenGate: $6.50M EE + RAC + GoldenGate: $8.80M |
These are list-price arithmetic benchmarks for 100 Processor licenses of each listed component. Actual estate licensing still depends on licensable Processors, core factors, topology, option use, GoldenGate source/target rules, and contract terms. |
| PostgreSQL + PatroniRELATIONAL · SELF-MANAGED | PostgreSQL software license: $0 Patroni software license: $0 PostgreSQL permits use without fee; Patroni is MIT licensed. |
$0 database/Patroni software licenseInfrastructure, DCS, support, backup, monitoring, labor, and operations are separate. | Software-license cost is zero. Total operating cost is not zero and cannot be derived from database count alone. |
| EDB PostgresRELATIONAL · MANAGED |
Advanced Server HA: $0.2568 / vCPU-hour
Advanced Server distributed HA: $0.3424 / vCPU-hour
EDB states cloud infrastructure is billed separately by the cloud provider when using the customer's cloud account.
|
100-vCPU benchmark:Advanced Server HA: ≈ $18,746/mo · $224,957/yr Distributed HA: ≈ $24,995/mo · $299,942/yr |
These figures use EDB's published per-vCPU database-service rates and 730 hours/month. Cloud infrastructure, storage, transfer, replica count, and data-node count remain separate. |
| Amazon RDS PostgreSQLRELATIONAL · AWS | AWS Prescriptive Guidance example: $742 / month Published AWS modernization example; us-east-1 with the source's stated instance, throughput, IOPS, and storage assumptions. |
100 identical AWS reference configurations:$74,200/mo · $890,400/yr | This is a 100× reference multiplication of AWS's published example, not a claim that 100 databases require 100 RDS instances. |
| Amazon RDS MySQLRELATIONAL · AWS | AWS Prescriptive Guidance example: $712 / month Published AWS modernization example; us-east-1 with the source's stated instance, throughput, IOPS, and storage assumptions. |
100 identical AWS reference configurations:$71,200/mo · $854,400/yr | This is a 100× reference multiplication of AWS's published example, not a claim that 100 databases require 100 RDS instances. |
| Aurora Global DatabasePOSTGRESQL / MYSQL · AWS |
AWS example — Standard: $664.88 / month
AWS example — I/O-Optimized: $861.80 / month
Example: 2 db.r6i.large in US East (N. Virginia), 1 in US West (Oregon), 80 GB in each Region, and AWS-stated I/O assumptions.
|
100 identical AWS examples:Standard $66,488/mo · $797,856/yr I/O-Optimized $86,180/mo · $1,034,160/yr |
This is exact arithmetic from AWS's published example. It is not a quote for your 100 databases and is not an engine-specific estate estimate. |
| MongoDB Atlas M30DOCUMENT · MANAGED | M30 base price: $0.54 / hour MongoDB states provider, Region, storage and usage affect cost. |
100 separate M30 clusters:$39,420/mo · $473,040/yr at 730 hours/month. | This is a 100-cluster base-price reference, not a 100-database TCO. Multiple databases can exist within a cluster. |
| Amazon DocumentDBDOCUMENT · AWS |
AWS Standard example: $449.42 / month
AWS I/O-Optimized example: $459.86 / month
Both use two db.r5.large instances and 50 GB data; AWS's Standard example uses 200M I/Os/month while the I/O-Optimized example uses 1,000M.
|
100 identical AWS examples:Standard $44,942/mo · $539,304/yr I/O-Optimized $45,986/mo · $551,832/yr |
Exact multiplication of two different AWS examples. Do not use the two totals as an equal-workload Standard-vs-I/O-Optimized comparison. |
The application requirement remains the design authority. Compatibility, availability, RTO/RPO, performance, security, support model, migration effort and operational ownership must be satisfied before cost can decide between viable platforms.
ENGINEERING TRACKS
Local database labs stay local. AWS-managed services stay cloud-native. The site does not blur those boundaries.
Cloud database engineering for Aurora PostgreSQL with focus on architecture, resilience, performance, upgrades, recovery, monitoring, and modernization.
Cloud-native MySQL-compatible engineering focused on topology, failover, read scaling, binlog/CDC, capacity, upgrades, and operational evidence.
Self-managed PostgreSQL engineering centered on internals, performance, replication, backup/recovery, and operational troubleshooting.
Primary, HADR standby, and quorum/utility roles for safe exploration of availability, recovery, performance, and operational behavior.
Primary, standby, and utility/test roles for recovery engineering, Data Guard concepts, patching discipline, and database-native operations.
Use automation for repeatable discovery and orchestration while keeping database-native operations in the correct database utilities.
MongoDB-compatible document database engineering with compatibility assessment, migration design, validation, security boundaries, and recovery evidence.
AWS DMS, infrastructure automation, monitoring, and controlled modernization workflows around the database platforms.
NON-NEGOTIABLES
This site publishes concepts and sanitized examples. It must never contain real credentials, private keys, account IDs, internal hostnames, production data, or unreviewed destructive commands.
Discover facts and establish evidence before changing configuration.
Require explicit approval for restore, failover, corruption, and other impact tests.
Never run destructive learning scenarios against production systems.
Record versions, outputs, timestamps, assumptions, and observed results.