Why Amazon Is Phasing Out Oracle Databases: Inside the Cloud Migration Battle
Amazon is rapidly shifting its enterprise workloads from Oracle's proprietary databases to its own AWS services, planning to retire Oracle software by early 2020, a move that highlights the intensifying competition between the two tech giants and the broader shift toward cloud-native infrastructure.
Amazon’s Migration Away from Oracle Database
Internal sources indicate that Amazon is moving the majority of its infrastructure from Oracle‑based services to its own Amazon Web Services (AWS) platform. The target is to discontinue use of Oracle’s proprietary database software by the first quarter of 2020.
Timeline and Scope
Initial disengagement from Oracle began 4–5 years ago.
The remaining Oracle‑dependent components of Amazon’s core retail operations are expected to be migrated within 14–20 months.
Completion of the full migration was projected for mid‑2019, with the final cut‑over to AWS‑native databases slated for Q1 2020.
Technical Drivers for Migration
Oracle’s database technology was reported to be unable to scale to Amazon’s performance and throughput requirements.
Oracle’s recent database innovations had stalled, offering limited new capabilities for large‑scale cloud workloads.
Aurora and Database Migration Service (DMS)
In 2014 AWS launched Aurora, a relational database service designed to be compatible with Oracle‑compatible workloads while offering higher performance and lower latency. Notable enterprise adopters include Capital One, Expedia, General Motors, and Verizon.
AWS also provides the Database Migration Service, which supports migration from Oracle to Aurora or other AWS databases. According to AWS, DMS has facilitated the migration of over 80,000 databases to the AWS cloud.
Operational Challenges Highlighted by Prime Day
During the 2017 Prime Day event, Amazon experienced capacity‑related failures that caused widespread access errors for shoppers.
Post‑mortem analysis linked the outage to a crash of an internal storage service named Ser, which underpins retail and digital services.
These incidents underscored the difficulty of handling sudden traffic spikes even with a large‑scale cloud infrastructure.
Oracle’s Response
Oracle’s leadership highlighted that Amazon had continued to spend significant sums on Oracle technology—approximately $60 million in the past year and several hundred million dollars overall.
Oracle’s statements emphasized that AWS lacks database capabilities that fully match Oracle’s feature set.
Larry Ellison warned that Amazon’s cloud platform was not yet ready to sustain peak workloads such as Prime Day, and that large Oracle customers moving to the cloud would still rely on Oracle‑provided services.
Overall, the migration reflects a broader industry shift toward cloud‑native database solutions and illustrates the technical and operational challenges involved in replacing entrenched enterprise database platforms.
ITPUB
Official ITPUB account sharing technical insights, community news, and exciting events.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
