Initiative Dashboard

This Initiative proposes to deprecate & EOL the BI Connector option in Atlas (“Atlas BIC”) and instead drive users to Atlas Data Lake for SQL (“ADL SQL”) access to Atlas clusters.

There are currently ~850 Atlas projects with BIC enabled (generating ~$90k MRR in BIC usage). However, Atlas BIC has been in maintenance mode for a while by not implementing enhancements. This has helped free the Connector and Atlas teams to put cycles elsewhere, outside of only doing the required minimum level of maintenance.

Last year, read-only SQL was integrated into Atlas Data Lake as a Beta and we want to make ADL SQL the primary method of SQL access for our users. By EOL’ing Atlas BIC, the Connector team can focus SQL enhancements in a single place which enables us to have a consistent & holistic SQL story for products available in MongoDB Cloud. Therefore, we need to define the steps to stop offering Atlas BIC and drive users to ADL SQL instead.

Once ADL SQL is GA and we announce Atlas BIC deprecation, we cap net-new adoption of Atlas BIC by disallowing the creation of new Atlas BIC instances other than for projects that already have an enabled BIC instance. All net-new Atlas SQL deployments go through ADL, but existing Atlas BIC instances still function.

To be clear, there are fundamental differences between ADL SQL and Atlas BIC (e.g., SQL dialect and client compatibility) which will impact a user’s ability to migrate between services (see Product Features for a comparison). We recommend a period of overlap where both Atlas & ADL endpoints are available for users to adjust & migrate their workloads to the ADL SQL endpoint. After that period, we decommission Atlas BIC instances.