Migrate to the Data API

If you are new to Astra DB or the Data API, this page provides guidance on moving from a similar API or tool to the Data API.

Compare the Astra DB Data API with MongoDB

Both MongoDB and Astra DB provide APIs to interact with your data.

If you are familiar with MongoDB’s API, you will find many similarities in the Astra DB Data API, and you can quickly get started with Astra DB. However, the Data API isn’t fully compatible with MongoDB’s API.

Connect

You can interact with the Astra DB Data API directly through HTTP or through the Python, TypeScript, and Java clients.

While there are many MongoDB drivers, the MongoDB Data API and HTTPS endpoints are deprecated. Astra DB continues to support HTTPS as a viable option for interacting with the Astra DB Data API and DevOps API.

Both the MongoDB drivers and Astra DB Data API clients require you to instantiate a client object, but the manner of authentication is different:

  • MongoDB requires a connection URI, which can include authentication parameters.

  • Astra DB requires an application token and your database’s API endpoint. The permissions required for the token depend on the commands you want to execute

For more information, see Get started with the Data API and Intro to Astra DB APIs.

Timeouts

The Astra DB Data API clients do not cancel a running server job upon hitting the timeout limit. Instead, the client stops waiting for the server-side operation and proceeds to the next client-side command.

Client code example

Astra DB Data API client code is similar to MongoDB driver code. The following examples compare some MongoDB Node.js driver code with Astra DB TypeScript client code. Both examples query a database, and they both assume you have a database with some data loaded and ready to query.

  • MongoDB Node.js driver

  • Astra DB TypeScript client

const { MongoClient } = import("mongodb");

// Replace the uri string with your connection string.
const uri = "CONNECTION_STRING_URL";

const client = new MongoClient(uri);

async function run() {
  try {
    const database = client.db('sample_mflix');
    const movies = database.collection('movies');

    // Query for a movie that has the title 'Back to the Future'
    const query = { title: 'Back to the Future' };
    const movie = await movies.findOne(query);

    console.log(movie);
  } finally {
    // Ensures that the client will close when you finish/error
    await client.close();
  }
}
run().catch(console.dir);
import { DataAPIClient } from "@datastax/astra-db-ts";

const token = "ASTRA_DB_APPLICATION_TOKEN";
const endpoint = "ASTRA_DB_API_ENDPOINT";

const client = new DataAPIClient(token);

async function run() {
  try {
    const database = client.db(endpoint);
    const movies = database.collection("movies");

    // Query for a movie that has the title Back to the Future
    const query = { title: "Back to the Future" };
    const movie = await movies.findOne(query);

    console.log(movie);
  } finally {
    // Ensures that the client will close when you finish/error
    await client.close();
  }
}
run().catch(console.dir);

Architecture

While MongoDB and Astra DB both use a four-layer architecture, the names of these layers and some underlying functionality are different.

These differences exist because Astra DB is based on Apache Cassandra®, which uses keyspaces to group tables (and collections) in a database. In contrast, MondoDB organizes data using databases and collections.

MongoDB architecture layer Astra DB architecture layer Definition

Cluster

Database

The top-level container for your data.

Database

Keyspace

A logical container for collections of data.

Collection

Collection

A group of documents.

Document

Document

A record in a collection.

Command compatibility matrix

The following table compares command compatibility at different architecture layers:

Astra DB layer MongoDB command Astra DB command Comments

Databases

Access a database

Keyspaces

See Database

In Astra DB, when you connect to a database, you set a working keyspace. You can change the working keyspace, but you don’t need an extra command to establish the initial working keyspace.

Collections

Create a collection

Collections

Access a collection

Collections

List collections

The Astra DB Data API clients also provide a List collection names command.

Collections

Delete a collection

Astra DB doesn’t support methods like collection.rename(). Collection configuration is immutable after creation.

Documents

Insert one

Documents

Insert many

Astra DB supports ordered inserts, among other options.

Documents

Find one

Documents

Find multiple

There are many nuances to the find command and the compatibility of filter, limit, sort, and skip options. For more information, see Sort operations and Find documents using filtering options.

Documents

Find distinct

This command is a client-side operation that can have performance and billing implications when searching large datasets.

Astra DB doesn’t offer direct support for this command in HTTP. However, you can use Find with jq or another utility to extract desired values from the response. This is effectively the same approach taken by the clients.

Documents

Update one

For a more verbose response that includes the original or updated document, use the Astra DB Data API Find one and update command.

upsert is supported.

Documents

Update many

upsert is supported.

Documents

Replace one

The Astra DB Data API clients also provide a Replace one command, which performs the same operation but returns only the outcome of the operation. This command isn’t available over HTTP, but you can use a projection to minimize the response from findOneAndReplace.

Documents

Count documents

Astra DB supports filtered and unfiltered counting. This command isn’t recommended for counting large datasets. For more information, see Count documents.

Documents

Estimated document count

Documents

Delete one

For a more verbose response that includes the deleted document, use the Astra DB Data API Find one and delete command.

Documents

Delete multiple

Indexing

Indexing is significantly different in MongoDB and Astra DB:

MongoDB function Astra DB function Comments

Multiple index types

Single field indexes only

Automatic indexing for _id only. You must create and manage additional indexes.

Automatic indexing for all document properties with the option for selective indexing.

Dynamic index management

No dynamic index management.

In Astra DB, indexing is a collection-level configuration that you set when you create a collection. Collection settings are immutable after creation.

ObjectIds and UUIDs

The Astra DB Data API supports a variety of _id types, including MongoDB’s ObjectId type. For more information, see Document IDs and The defaultId option.

Astra DB supports Vector search similar to MongoDB Atlas Vector Search. However, whereas Atlas Vector Search is part of an aggregation pipeline, Astra DB’s vector search is directly integrated in commands, like Find, as a sort clause.

Additionally, Astra DB can generate embeddings on demand with vectorize. You can use $vectorize to run a vector search based on an embedding generated from any text string.

The Astra DB Data API offers commands and parameters for vector search and vectorize, including collection parameters for vectorize and the $vector and $vectorize reserved fields.

Operators

The Astra DB Data API doesn’t support all MongoDB operators. Unsupported operators include, but are not limited to, the following:

  • $type

  • $elemMatch

  • Evaluation operators, such as $expr, $jsonSchema, $mod, $regex, and $where

  • Bitwise operators, such as those prefixed with $bits

  • Geospatial operators, such as those prefixed with $geo and geometry specifiers

  • Miscellaneous operators $comment, $rand, and $natural

The Astra DB Data API doesn’t support $nor, but you can use compound $not and $and operators instead.

For more information and examples, see Operators, $date, and the references for the methods that use these operators, such as Find.

Response modifiers

The Astra DB Data API offers options to modify the order and content of a response beyond query filters:

In the Astra DB Data API, some combinations of filter, limit, sort, and skip are incompatible. For more information, see Sort operations.

Cursors and pagination

Like the MongoDB drivers, the Astra DB Data API clients use cursors to manage large responses. Over HTTP, the Astra DB Data API uses pagination.

For more information and examples, refer to the references for commands that return cursors or pagination, such as Find.

MongooseJS

You can use the Astra DB Data API with MongooseJS. For more information, see Integrate MongooseJS with Astra DB Serverless.

Administration

You can use the Astra DB Data API clients to perform administrative operations on databases and keyspaces:

  • Create a database

  • Get database information

  • List databases

  • Delete a database

  • List keyspaces

  • Create a keyspace

  • Delete a keyspace

These commands are also available over HTTP through the DevOps API API. For more information, see Databases reference.

You can’t use MongoDB drivers for database or cluster administration. However, MongoDB offers other programmatic options for these tasks.

Outside of database operations, Astra DB offers administrative tools similar to those offered by MongoDB:

MongoDB tool Astra DB tool Comments

Atlas App Services Admin API

Some DevOps API functions are also available through the Astra DB Data API clients. For more information, see Databases reference.

HashiCorp Terraform MongoDB Atlas Provider

For more information, see Integrate HashiCorp Terraform with Astra DB Serverless.

Atlas CLI

Astra CLI

Incompatible functionality

The Astra DB Data API doesn’t provide a mechanism for change streams, but you can use the Astra DB CDC connector external to the Astra DB Data API. To enable this feature for Serverless (Vector) databases, contact DataStax Support.

The following MongoDB driver functionality isn’t available in Astra DB or the Astra DB Data API:

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000, info@datastax.com