/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Amazon says its consumer business has decommissioned its final Oracle database and migrated 75 petabytes in ~7,500 Oracle DBs to multiple AWS database services

AWS said that Amazon's consumer business has decommissioned its final Oracle database and migrated 75 petabytes of data …

ZDNet Larry Dignan

Context & Ripple Effects

This closes a loop opened in August 2018, when reports surfaced that Amazon planned to move its infrastructure entirely off Oracle's proprietary database software by early 2020, followed by Amazon's own disclosure that its services would run 97% of its mission-critical databases. The completion claim — 75 petabytes across roughly 7,500 Oracle databases shifted to multiple AWS services — is also the payoff of tooling AWS built for everyone else, having made its Database Migration Service generally available back in 2016.

The competitive subtext is sharp: AWS spent years positioning itself against legacy vendors like Oracle, and Amazon used its own consumer business as the reference migration. The irony is that in 2024 the two companies partnered to launch Oracle Database@AWS, letting customers run select Oracle products inside AWS — coexistence after the breakup.

First-order effects

  • Amazon's consumer business now runs its database workloads entirely on AWS services, removing an internal dependency on a direct competitor's flagship product and giving AWS a completed at-scale case study to show enterprise customers weighing their own exits.

Second-order effects

  • Oracle loses its highest-profile internal customer as a proof point against cloud-database switching, pressuring it toward accommodation — which is arguably what the later Oracle Database@AWS partnership reflects, meeting Oracle workloads where customers' clouds already are.

Third-order effects

  • If the largest cloud buyer can fully unwind ~7,500 proprietary database deployments using the vendor's own migration tooling, the pattern points toward hyperscale clouds consolidating enterprise data workloads while legacy database vendors shift from defending installations to distributing through those same clouds.

The trend: Enterprise databases are migrating from licensed proprietary systems into hyperscale cloud-native services, with former rivals ending up as distribution partners once the migration wave crests.

Discussion

  • @jeffawilke Jeff Wilke on x
    We just shut down the last Oracle database connected to Amazon's consumer business and migrated 75 petabytes - from more than 100 teams - to AWS. Instead of saying “I have more urgent things to do,” teams worked with the long-term benefit in mind. https://aws.amazon.com/...
  • @halberenson Hal Berenson on x
    If people want to know how a “company” can go from one of Oracle's largest customers to not using them at all the real key is having a CEO like @jeffawilke. He made it a priority for the entire consumer organization, and kept it there for the few years it took to pull it off. htt…
  • @_joemag Joe Magerramov on x
    A trip down the memory lane. When I joined Amazon 14 years ago, my very first project was to add a simple feature to one of our backend services. The service was backed by an Oracle database, and the feature required addition of a new table, and a few extra columns. 1/n https://t…
  • @jonmasters Jon Masters on x
    Never underestimate Bezos. Especially not when you call him out repeatedly. Because this happens. https://twitter.com/...
  • @joshuaseattle @joshuaseattle on x
    And we're super close on #AWS to the same milestone. Migrating off #Oracle to purpose built cloud-scale DBs for the AWS services I owned brought the same benefits - better speed, cost, latency & availability. Nothing to lose but the onerous licensing and audits #ByeFelicia https:…
  • @jim_scharf Jim Scharf on x
    I had the honor of participating in this from the @dynamodb side. Not only is this better for Amazon Consumer, in the process, it also forced @dynamodb to become even better, benefiting ALL customers. https://twitter.com/...
  • @pankajontech Pankaj Mishra on x
    Some deep enterprise lessons from Amazon ditching Oracle: Migration Complete - Amazon's Consumer Business Just Turned off its Final Oracle Database https://aws.amazon.com/... via @awscloud
  • @daveleebbc Dave Lee on x
    I've been putting off backing up my photos for a year, and then I read this https://aws.amazon.com/...