Amazon removes the database scaling wall
When Amazon introduced S3 in March 2006 I knew I would use it and I was sure a lot of other developers would. I saw it as a solution to a problem we all have — storage that scales up when needed, and scales down when not.
Context & Ripple Effects
Amazon has been assembling its web-services stack piece by piece since it introduced S3 in March 2006 as storage that scales up when needed and down when not — coverage of S3's service model framed it as solving a problem every developer shares. The missing layer was a database: until this week, developers renting AWS compute and storage still had to run their own relational database or buy one.
SimpleDB, formerly known as SDS after years of development under NDA, enters limited beta within weeks, and the framing across coverage is aggressive: TechCrunch casts it as Amazon taking on Oracle and IBM directly, with GigaOM's SimpleDB explainer arguing the point is removing the need for costly database administrators altogether.
First-order effects
- Developers building on AWS can now store structured data without provisioning servers, licenses, or a DBA — the scaling wall the headline names is removed for anyone already using EC2 and S3.
Second-order effects
- Oracle and IBM face a competitor whose database is priced as a utility rather than licensed per seat, pressuring their enterprise pricing models at exactly the tier where startups and small teams live.
Third-order effects
- If the pattern holds, cloud vendors stop selling components and start selling entire IT departments on demand — with the database administrator role, as TechCrunch notes, the first job title the model displaces.
The trend: Cloud infrastructure is expanding from raw storage and compute into managed application services, letting Amazon assemble a full substitute for the traditional enterprise IT stack.