/
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 SimpleDB 101 & Why It Matters

Amazon continues to amaze us with its Amazon Web Services series of offerings.  The latest is SimpleDB, which will be available in limited beta in a few weeks.  And it is bound to have a major impact on web infrastructure.  As Amazon says in its email to existing developers:

GigaOM Nitin Borwankar

Context & Ripple Effects

SimpleDB completes the arc Amazon started with S3: storage first, then compute, and now a queryable database layer, all delivered as metered web services. The service had been gestating for years under the codename SDS behind NDAs, and its limited beta lands alongside a busy Amazon news cycle that includes the sold-out $400 Kindle.

The framing across same-day coverage is pointed: TechCrunch reads the move as Amazon taking on Oracle and IBM, arguing that a schemaless, admin-free database priced by usage attacks the costliest layer of the traditional enterprise stack — the DBA. Between the Lines picks up the same thread under an economics banner, which suggests the story travelled as a pricing-and-labor disruption story rather than a product launch.

First-order effects

  • Developers in the limited beta get a database with no servers to provision and no administration overhead, paying only for what they use — directly undercutting the licensing-plus-DBA cost structure Oracle and IBM sell on.
  • Oracle and IBM face their first credible competition at the low end of the database market from a company whose infrastructure business already has developer mindshare via S3 and EC2.

Second-order effects

  • Enterprise database vendors are pushed to respond with hosted or utility-priced offerings of their own, because the comparison buyers will now make is per-query usage versus six-figure licenses plus administrator salaries.
  • The pool of work available to database administrators shifts: routine scaling, patching, and capacity planning for small-to-mid web applications moves into the platform, concentrating DBA demand on genuinely complex enterprise deployments.

Third-order effects

  • If usage-priced databases prove viable, the database becomes another commodity layer rented from infrastructure providers rather than software installed and owned — the same absorption pattern S3 applied to storage, extended to data management.
  • Amazon's position as default provider of compute, storage, and now data services makes AWS a de facto operating layer for web startups, raising questions regulators and enterprises will eventually have to address about concentration in one vendor.

The trend: Cloud providers are absorbing the enterprise software stack one layer at a time — storage, then compute, now databases — converting licensed products administered by specialists into metered utilities run by the platform itself.