API stability
API stability is the degree to which an interface’s contract and behavior remain compatible enough for existing clients to continue functioning across changes and versions.
MongoDB 8.0 in Action, Third Edition
The MongoDB Stable API is a versioned API compatibility contract that preserves supported command behavior across MongoDB server upgrades.
- How it is used
- Stabilizes application behavior during MongoDB server, driver, and Atlas upgrades.
- How deep it goes
- Defines apiVersion, explains compatibility and deprecation isolation, and lists supported commands without detailing internal negotiation.
- Examples
- Uses mongosh connection options, a PyMongo MongoClient, and a command-coverage table as concrete configuration examples.
- What you can do after
- Operate MongoDB clients across server upgrades by configuring apiVersion and checking whether required commands belong to the Stable API.
Read how MongoDB 8.0 in Action, Third Edition explains API stability →
Vanilla Web
A stable API is a web API whose behavior and availability are sufficiently established for dependable use across supported browsers.
- How it is used
- Guides browser API choices by separating dependable core features from optional capabilities with limited support.
- How deep it goes
- Distinguishes API support categories and recommends progressive enhancement and feature detection, without detailing API internals.
- Examples
- Names Fetch, Web Storage, and Geolocation as stable APIs and demonstrates checking for the Permissions API.
- What you can do after
- Evaluate API support with Baseline, MDN, or Can I Use, then guard optional features with feature detection.
Also covered in
- Automating API Delivery
- Microservices Patterns, Second EditionIn early access (MEAP)
Related concepts
- pymongoused by · PyMongo is the official Python driver for connecting applications to MongoDB and performing database operations.
- backward compatibilityproduces · Backward compatibility is the property of a newer or changed system remaining usable by existing clients, code, data, or integrations that depend on earlier interfaces or behavior.
- clientuses · A client is a person, organization, device, or software component that receives or uses a product, service, resource, or functionality provided by another party or system.
- mongoshused by · mongosh is MongoDB’s interactive command-line shell for connecting to deployments and executing database commands and queries.
Questions about API stability
What is API stability?
API stability is the degree to which an interface’s contract and behavior remain compatible enough for existing clients to continue functioning across changes and versions.
Which Manning books explain API stability?
MongoDB 8.0 in Action, Third Edition and Vanilla Web.
What is the difference between API stability and experimental API?
API stability is the degree to which an interface’s contract and behavior remain compatible enough for existing clients to continue functioning across changes and versions. An experimental API is a web API whose specification, implementation, or browser availability is still undergoing development and evaluation.
What is API stability also called?
API stability is also called stable API.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

