OpenAI’s latest Habitat engineering report describes the database decisions behind its online storage platform. The account focuses on Azure Cosmos DB and the tradeoff between sharing resources efficiently and isolating workloads when something becomes unusually busy.
A circular tenancy journey
OpenAI says Habitat moved from a shared Cosmos DB container to separate backing containers, then returned to a shared-container default. This is a description of the company’s experience, rather than a recommendation that every application use the same database layout.
For another engineering team, the useful question is which failure mode a proposed change actually addresses. Is the problem insufficient total capacity, unpredictable growth in one workload or an expensive requirement to plan each service separately? Those are different diagnoses even when they appear as the same slow request to a user.
Isolation moves responsibility
The report describes dedicated containers as a way to limit the impact of one workload on another. It also explains that single tenancy makes product teams responsible for capacity planning and can lead to overprovisioning. Shared infrastructure centralizes that work but introduces noisy-neighbour problems.
A design review can make those costs visible without assuming one arrangement wins universally. Record who owns scaling, what signal triggers an intervention and how an incident in one tenant is measured. Compare both the reliability boundary and the operational effort needed to maintain it.
Read scale claims in their context
OpenAI describes Habitat as supporting access across 40 geographic regions and more than one billion users. Those are the company’s reported operating conditions, not a benchmark of another organization’s likely performance.
The transferable value is the decision process. Before copying a container strategy, test a representative workload, identify the required isolation and document the migration and rollback path. A successful architecture at one scale can reveal questions worth asking without supplying the answer for a different application.