/
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 and VMware debut a version of database management software for companies that use on-premises databases from Microsoft, Oracle, MariaDB, and others

Jordan Novet / CNBC :

CNBC Jordan Novet

Context & Ripple Effects

This launch is the productization of a migration arc CNBC has been tracking since August, when sources reported Amazon's plan to move its infrastructure entirely off Oracle's proprietary databases by early 2020. Rather than just fleeing Oracle internally, Amazon is now selling the escape route: with VMware, whose infrastructure software came to AWS through their 2016 partnership, it debuts tooling that manages on-premises Microsoft, Oracle, and MariaDB databases — the exact estates enterprises would need to unwind before moving to the cloud.

The move also deepens a relationship already extended geographically via VMware Cloud for AWS in Europe, and it positions VMware as the bridge between corporate data centers and AWS rather than merely a virtualization layer inside them.

First-order effects

  • Enterprises running on-premises Oracle, Microsoft, and MariaDB databases gain an AWS-VMware-backed management layer, lowering the operational barrier to migrating those workloads to AWS.
  • VMware expands beyond virtualization into database management for AWS customers, converting its installed base of on-premises infrastructure relationships into a cloud migration funnel.

Second-order effects

  • Oracle and Microsoft face erosion at the management layer around their on-premises databases — the same displacement Amazon was executing internally per its own migration milestones reported later that year.
  • Database vendors are pushed toward meeting clouds on the clouds' terms, a pattern that culminated years later when Oracle and AWS launched Oracle Database@AWS, following Oracle's similar arrangements with Azure and Google Cloud.

Third-order effects

  • If the pattern holds, hyperscalers absorb the enterprise database administration layer itself, shifting vendor leverage from license ownership to whichever platform controls migration tooling and runtime — with incumbents surviving only by embedding their databases inside rival clouds.
  • Hybrid-management partnerships like this one become the standard mechanism for cloud capture of legacy data centers, forcing every major database vendor to negotiate distribution deals with the platforms displacing them.

The trend: Cloud providers are turning internal database migrations into external products, using partners like VMware to pull on-premises Oracle and Microsoft database estates onto their platforms.