Atlas Data Federation Overview

Key Concepts

Atlas Data Federation Architecture

When you use Atlas Data Federation, federated database instances exist within regional VPCs. All federated database instance data traffic, whether to Atlas clusters or cloud provider object storage, is TLS encrypted. TLS encryption is the primary form of network security available with Atlas Data Federation. If your federated database instance and data source (Atlas cluster, S3, Blob, Google Cloud Storage) use the same cloud provider, data traffic either traverses the cloud provider's network infrastructure, or the public internet, depending on the cloud provider's documented network service capabilities. If your federated database instance and data source are on different cloud providers, data traffic traverses the public internet.

click to enlarge

The Data Plane in the preceding diagram is where your data resides. You can configure Atlas Data Federation to access data in a variety of storage services. Specifically, you can configure Atlas Data Federation to access data in your AWS S3 buckets across AWS regions, Azure Blob Storage containers, Google Cloud Storage buckets, Atlas clusters, HTTP and HTTPS URLs, and Atlas Online Archives. To learn more about configuring Atlas Data Federation to access your data stores, see Define Data Stores for a Federated Database Instance.

You can then set up role-based access control for your federated database instances. You can control how your client connects to your federated database instance, either through a global connection option or by pinning it to a specific region. To learn more, see Configure Connection for Your Federated Database Instance.

Atlas Data Federation preserves data locality and maximizes local computation, where possible, to minimize data transfer and optimize performance. The Compute Plane in the preceding diagram shows where Atlas Data Federation processes all requests. Atlas Data Federation provides an elastic pool of agents in the region that is nearest to your data where Atlas Data Federation can process the data for your queries. To learn more about supported regions, see Atlas Data Federation Regions.

Atlas Data Federation doesn't persist data inside the system and once your query is processed, it only stores the metadata in your federated database instance. This allows you to comply with data sovereignty regulations and ensures that your data is stored and processed in compliance with legal requirements.

The Control Plane in the preceding diagram, which is the same as the Atlas Control Plane, is where Atlas Data Federation balances user requests and aggregates final results.

Atlas Data Federation executes certain parts of a query directly on the underlying storage service, rather than transfer all of the data to the compute nodes for processing. Additionally, when you execute a query, it is first processed by a Data Federation front-end component, which plans the query and then distributes it to the nodes in the backend. The backend nodes then access your data store directly to execute the query logic and return the results back to the front-end. This process reduces the amount of data to move around, thereby making the whole process faster and cheaper. To learn more, see Query a Federated Database Instance.

To optimize the performance of your queries, Atlas Data Federation does the following:

• For Cloud Object Storage, it uses data partitioning to select the files that it needs to process based on query parameters. To learn more, see Define Path for S3 Data and Use Partition Attribute Types. Additionally, it uses Parquet metadata to reduce the amount of data it scans from parquet files using row group selection or column projection. To learn more, see Parquet Data Format.

• For Atlas clusters, it tries to "push down" as much of the query to the cluster as possible. For example, if your aggregation pipeline has a $match stage and if it can be processed locally, Atlas Data Federation tries to process that stage in the Atlas cluster and only returns the resulting documents back to the federated layer for processing subsequent stages. To learn more, see Querying Data in Your Atlas Cluster.

To learn more, see Optimize Query Performance.

You can connect to Atlas Data Federation using MongoDB language-specific drivers, mongosh, and Atlas SQL. To learn more, see Connect to Your Federated Database Instance.

Sample Uses

You can use Atlas Data Federation to:

• Copy Atlas cluster data into Parquet or CSV files written to AWS S3 buckets or Azure Blob Storage.

• Query across multiple Atlas clusters and online archives to get a holistic view of your Atlas data.

• Materialize data from aggregations across Atlas clusters, AWS S3 buckets, and Azure Blob Storage.

• Read and import data from your AWS S3 buckets or Azure Blob Storage into an Atlas cluster.