MongoDB 1.0 Released — The Document-Oriented Symbol of the NoSQL Movement

On 11 February 2009, the New York startup 10gen released MongoDB 1.0. Instead of rows and columns, it stored JSON-style documents—a document-oriented database. Then unknown, this design would within a few years become the public face of the whole "NoSQL movement".

10gen's Origins — Escaping DoubleClick

10gen's founders Dwight Merriman and Eliot Horowitz were the former CTO and an early engineer at the ad-tech company DoubleClick. At DoubleClick they had wrestled with web-scale real-time data processing—hundreds of thousands of QPS aggregating bid and serving logs—and had felt the scaling ceiling of conventional RDBMS (Oracle, MySQL) firsthand.

They founded 10gen in 2007. The original goal was a PaaS (Platform-as-a-Service), an AWS-style general-purpose cloud platform. The database layer they built underneath gradually looked, on its own, like the more promising product. In 2009 they dropped the PaaS plan, refocused as a database company, and released MongoDB 1.0.

The company name comes from "Tenth Generation"; "MongoDB" from "humongous". Together: a tenth-generation DB for huge data.

The Document Model — Nested Documents, not Tables

MongoDB's defining feature is that the unit of data is not a row but a BSON document. BSON is a binary form of JSON, and a single document can contain nested objects, arrays, and typed values (date, ObjectID, and so on).

{
  _id: ObjectId("..."),
  name: "Alice",
  orders: [
    { item: "Book", price: 1500, date: ISODate("2024-01-15") },
    { item: "Pen",  price: 200,  date: ISODate("2024-02-03") }
  ],
  address: { city: "Tokyo", zip: "100-0001" }
}

What an RDBMS would model as four tables joined together (user, order, order_item, address) fits into one document. The design choice is to align the application's object structure with the database's storage structure, attacking the object-relational impedance mismatch that makes ORM frameworks so awkward.

MongoDB is also schemaless: no need to declare a table layout in advance, and documents of varying shape can coexist in the same collection. For agile teams whose schemas shift week to week, this is a strong feature.

The NoSQL Movement — A Convergence in 2009

2009 was also the year "NoSQL" entered industry vocabulary. In June, a NoSQL meetup in San Francisco brought together MongoDB, Cassandra (open-sourced from Facebook in 2008), CouchDB (2005-), Redis (2009-), and other newcomers.

The context was a sense that RDBMS were running out of headroom for web-scale services. Google's Bigtable paper (2006) and Amazon's Dynamo paper (2007) had publicly argued that distributed environments require eventual consistency instead of ACID. The view that "ACID and the relational model are not absolutes" became NoSQL's theoretical backbone.

Inside that wave, MongoDB took the role of the document-oriented flagbearer. Alongside Cassandra (column-family), Redis (key-value), and Neo4j (graph), it became one of the canonical "not-an-RDBMS" choices.

Rapid Adoption and Sharp Criticism — The ACID Argument

In the first half of the 2010s, MongoDB spread fast. Foursquare, Craigslist, The New York Times, eBay, Shutterstock—adopters ranged from startups to enterprises.

But the critiques were equally sharp. Early MongoDB defaulted to fire-and-forget writes: db.users.insert() could return success while the data evaporated. Sarah Mei's 2013 blog post "Why You Should Never Use MongoDB" argued that the document model could not handle many-to-many relations properly, and was read everywhere.

10gen (renamed MongoDB Inc. in 2013) answered the criticism with persistent engineering. MongoDB 3.0 in 2015 made the WiredTiger storage engine (B-tree with compression, row-level concurrency control) the default. Version 4.0 in 2018 added multi-document ACID transactions, extended to distributed transactions in 4.2 (2019). The flagbearer of an anti-ACID movement ended up adopting ACID—a fitting microcosm of NoSQL's evolution overall.

2017 IPO and Today

In October 2017 MongoDB Inc. went public on NASDAQ. Priced at US$24, it closed day one at US$32.07 for a roughly US$1.8 billion market cap. By 2024 annual revenue is around US$2 billion, and market cap has ranged from roughly US$15 billion to US$35 billion depending on the quarter.

MongoDB Atlas (2016-), the multi-cloud managed service running on AWS, Azure, and GCP, has grown to roughly 70 per cent of revenue. Open-source upstream plus paid managed downstream: this is now one of the standard revenue models for open-source companies, echoed by Snowflake, Confluent, and Databricks.

What 11 February 2009 Means

The release of MongoDB 1.0 was more than a product launch. It was the moment when the idea "let the database schema match the shape of the application's data" moved out of research papers and Google's internal systems and into an OSS download anyone could install in five minutes.

The 40-year axiom "data is a table", set by the relational model, was joined by another axiom: "data is a document". 11 February 2009 was one of the days that made that pairing real. Firestore, DynamoDB Document Mode, the MongoDB API in Cosmos DB, PostgreSQL JSONB—document-oriented thinking has settled into the database world as a permanent option.