powersync-ja · cahofmeyr · Jan 24, 2025 · Jan 24, 2025
diff --git a/installation/app-backend-setup.mdx b/installation/app-backend-setup.mdx
@@ -26,3 +26,7 @@ See [Authentication Setup](/installation/authentication-setup) for details.
 See our [Example Projects](/resources/demo-apps-example-projects#custom-backend-examples) page for examples of custom backend implementations (e.g. Django, Node.js, etc.)
 
 For Postgres developers, using [Supabase](/integration-guides/supabase-+-powersync) is an easy alternative to a custom backend. Several of our demo apps demonstrate how to use [Supabase](https://supabase.com/) as the Postgres backend.
+
+### Hosted/Managed Option for MongoDB
+
+<Tip>For users using MongoDB as a source backend database, an alternative option to running your own backend is to use CloudCode, a serverless cloud functions environment provided by us. We have a template that you can use as a turnkey starting point. See our [documentation here](/usage/tools/cloudcode).</Tip>
diff --git a/installation/database-connection.mdx b/installation/database-connection.mdx
@@ -139,8 +139,8 @@ PowerSync deploys and configures an isolated cloud environment for you, which ca
 **Note**: PowerSync automatically selects the "Beta" version of the Service when adding a MongoDB connection while MongoDB support is in a beta release, as updates may be made against this version more frequently.
 
 Also see:
-- [MongoDB Atlas Migration Guide](/migration-guides/mongodb-atlas)
-- [MongoDB Setup](/installation/database-setup#mongodb-alpha)
+- [MongoDB Atlas Device Sync Migration Guide](/migration-guides/mongodb-atlas)
+- [MongoDB Setup](/installation/database-setup#mongodb-beta)
 
 ## <Icon icon="dolphin" iconType="solid" size="24"/> MySQL (Alpha) Specifics
 

diff --git a/installation/database-setup.mdx b/installation/database-setup.mdx
@@ -331,19 +331,16 @@ Notably, some "serverless Postgres" providers do not support logical replication
 
 ### Status of MongoDB support in PowerSync
 
-In PowerSync nomenclature, Beta means the package is ready to be used for production given you have adequately tested your use case. We typically don't make any breaking API changes when moving from Beta to V1 (learn more about feature states [here](/resources/feature-status)). 
+#### Beta Released — December 2024
 
-#### Alpha (Completed)
+Our MongoDB connector is [in Beta](https://www.powersync.com/blog/powersync-mongodb-connector-module-now-in-beta) as of December 2024 and is supported for use in production environments. See the [full release notes](https://releases.powersync.com/announcements/mongodb-as-a-backend-database-now-in-beta).
 
-#### Beta (Completed)
+In PowerSync nomenclature, Beta means the package is ready to be used for production given you have adequately tested your use case. We typically don't make any breaking API changes when moving from Beta to V1 (learn more about feature states [here](/resources/feature-status)).
 
-MongoDB is now supported for use in production environments.
 
-See [https://releases.powersync.com/announcements/mongodb-as-a-backend-database-now-in-beta](https://releases.powersync.com/announcements/mongodb-as-a-backend-database-now-in-beta) for the full release notes.
+#### V1 (In Progress — ETA 2025Q1)
 
-#### V1 (In Progress — ETA 2025H1)
-
-Our roadmap to V1 remains flexible and is strongly guided by customer feedback. Our focus includes enhancing usability, improving documentation such as migration guides, developing reference/demo applications, and exploring support for sharded MongoDB clusters and Atlas Private Endpoints. If you’d like to see any of these features, please visit our product roadmap and upvote/submit ideas.&#x20;
+Our roadmap to V1 remains flexible and is strongly guided by customer feedback. Our focus includes enhancing usability, improving documentation such as migration guides, developing reference/demo applications, and exploring support for sharded MongoDB clusters. If you’d like to see any of these features, please visit our product roadmap and upvote/submit ideas.
 
 ### Permissions required - MongoDB Atlas
 
@@ -403,7 +400,17 @@ db.runCommand( {
 db.getCollectionInfos().filter(c => c.options?.changeStreamPreAndPostImages?.enabled)
 ```
 
-Post-images can be configured for PowerSync Cloud instances under the connection settings in the Dashboard (right-click on your instance to edit it). For self-hosted PowerSync instances, configure post-images in the config.yaml file; see an example [here](https://github.com/powersync-ja/self-host-demo/blob/main/demos/nodejs-mongodb/config/powersync.yaml).
+Post-images can be configured for PowerSync Cloud instances under the connection settings in the Dashboard (right-click on your instance to edit it). For self-hosted PowerSync instances, configure post-images in the `config.yaml` file; see an example [here](https://github.com/powersync-ja/self-host-demo/blob/main/demos/nodejs-mongodb/config/powersync.yaml).
+
+### MongoDB Atlas private endpoints using AWS PrivateLink
+
+If you need to use private endpoints with MongoDB Atlas, see [Private Endpoints](/installation/database-setup/private-endpoints).
+
+
+### Migrating from MongoDB Atlas Device Sync
+
+For more information on migrating from Atlas Device Sync to PowerSync, see our [migration guide](/migration-guides/mongodb-atlas) and [this post](https://www.powersync.com/blog/migrating-a-mongodb-atlas-device-sync-app-to-powersync) on our blog.
+
 
 ## <Icon icon="dolphin" iconType="solid" size="24" /> MySQL (Alpha)
 

diff --git a/migration-guides/mongodb-atlas.mdx b/migration-guides/mongodb-atlas.mdx
@@ -1,8 +1,9 @@
 ---
-title: "MongoDB Atlas Migration Guide"
-description: "This page was last updated on 2024-12-27"
+title: "MongoDB Atlas Device Sync Migration Guide"
 ---
 
+<Info>We are currently working on a more detailed migration guide. In the meantime, the below guide provides high-level migration information.</Info>
+
 ## MongoDB Atlas deprecation
 
 In September 2024, MongoDB [deprecated](https://www.mongodb.com/docs/atlas/app-services/deprecation/#std-label-app-services-deprecation) the following services:
@@ -18,54 +19,53 @@ If you have MongoDB Atlas Device Sync deployed today, at a high level your archi
 
 ## PowerSync beta support for MongoDB
 
-As of December 2024, support for MongoDB as a backend database source is available in a beta release. This means that MongoDB replication is considered ready for production-use, provided that you have adequately tested your use cases.
+As of December 2024, support for MongoDB as a backend database source in PowerSync is available in [a Beta release](https://www.powersync.com/blog/powersync-mongodb-connector-module-now-in-beta). This means that MongoDB replication is considered ready for production-use, provided that you have adequately tested your use cases.
 
-It is currently available for testing in hosted or self-hosted environments:
+It is currently available in [PowerSync Cloud](https://www.powersync.com/pricing) and self-hosted environments:
 
-* Hosted by us: Refer to [Database Connection](/installation/database-connection#mongodb-beta-specifics)
-* Self-hosted using Docker Compose: An end-to-end demo app is [available here](https://github.com/powersync-ja/self-host-demo/tree/main/demos/nodejs-mongodb). Please refer to its README for further instructions.
+* **PowerSync Cloud**: Refer to [Database Connection](/installation/database-connection#mongodb-beta-specifics)
+* **Self-hosted**: An end-to-end demo app using Docker Compose is [available here](https://github.com/powersync-ja/self-host-demo/tree/main/demos/nodejs-mongodb). Please refer to its README for further instructions.
 
-Migrating to PowerSync's MongoDB module would take you to this: (new components in green)
+Migrating to PowerSync would take you to this: (new components in green)
 
 <Frame>
   <img src="/images/resources-2.png"/>
 </Frame>
 
-As you can see, this is not a point-and-click migration, however it does enable you to stay on MongoDB and those are the customers we are primarily interested in working with and supporting.
-
-### Notable comments on the architecture
+### Explanation of the migrated architecture
 
-1. PowerSync handles writes differently from reads. This is because developers typically want to have some business logic running on an authoritative server before allowing a client device to change data in the backend database.
-   1. Reads are partitioned using [Sync Rules](/usage/sync-rules)
-         1. Sync Rules are more flexible than MongoDB Realm Flexible Sync, but are defined server-side and not client-side.
-   2. Writes are queued locally on the device and sent to the backend sequentially.
-         1. The backend can be a very thin API layer or can contain significant amounts of logic — [it is up to the developer](/installation/app-backend-setup/writing-client-changes)
+1. PowerSync handles writes differently from reads. 
+   * **Reads:** The PowerSync Service connects to your MongoDB database and replicates data in real-time to PowerSync clients. Reads are partitioned using PowerSync's [Sync Rules](/usage/sync-rules)
+         * Sync Rules are more flexible than MongoDB Realm Flexible Sync, but are defined server-side and not client-side.
+   * **Writes:** The client-side application can perform writes directly on the local SQLite database. The writes are also automatically placed into an upload queue by the PowerSync client SDK. The SDK then uses a developer-defined `uploadData()` function to manage the uploading of those writes sequentially to the backend. In the `uploadData()` function, the developer calls their backend API.
+         * The backend can be a very thin API layer or can contain significant amounts of logic — [it is up to the developer](/installation/app-backend-setup/writing-client-changes)
 2. The PowerSync Service is generally [available](https://powersync.com/pricing) as a cloud-hosted service (PowerSync Cloud), or you can self-host using our Open Edition.
-3. The PowerSync Client SDKs use SQLite under the hood. While there is nothing on a protocol level preventing us from supporting Realm as a client-side database, we are waiting to see whether Realm becomes a community project or not before investing in it, since it would be a significant amount of work for us to support Realm on the client-side.
-   1. The client-side will most likely be where the bulk of migration work takes place for customers migrating from Atlas Device Sync to PowerSync.
-   2. Client-side queries are typically written in SQL. [ORM support](https://www.powersync.com/blog/using-orms-with-powersync) is available for our JavaScript ([React Native](/client-sdk-references/javascript-web/javascript-orm/overview) and [web](/client-sdk-references/javascript-web/javascript-orm/overview)) and Flutter/[Dart](/client-sdk-references/flutter/flutter-orm-support) Client SDKs.
+3. The PowerSync Client SDKs use **SQLite** under the hood. Even though MongoDB is a "NoSQL" document database, PowerSync's use of SQLite works well with MongoDB, since the [PowerSync protocol](/architecture/powersync-protocol) is schemaless (it syncs schemaless JSON data) and we dynamically apply a [client-side schema](/installation/client-side-setup/define-your-schema) to the data in SQLite using SQLite views.
+   * The client-side will most likely be where the bulk of migration work takes place for customers migrating from Atlas Device Sync to PowerSync. See [this post on our blog](https://www.powersync.com/blog/migrating-a-mongodb-atlas-device-sync-app-to-powersync) for a migration example. 
+   * Client-side queries are typically written in SQL. [ORM support](https://www.powersync.com/blog/using-orms-with-powersync) is available for our JavaScript ([React Native](/client-sdk-references/javascript-web/javascript-orm/overview) and [web](/client-sdk-references/javascript-web/javascript-orm/overview)) and Flutter/[Dart](/client-sdk-references/flutter/flutter-orm-support) Client SDKs.
 4. PowerSync piggybacks off your existing authentication, however, it uses JWTs. If you were using Atlas Device SDKs for authentication, you will need to implement an authentication provider.
 
 ### Migration steps
 
 <Tip>The blog post [Migrating a MongoDB Atlas Device Sync App to PowerSync](https://www.powersync.com/blog/migrating-a-mongodb-atlas-device-sync-app-to-powersync) can serve as a handy guide through the migration process.</Tip>
 
 1. Connect your database to an instance of the PowerSync Service:
-   1. Using PowerSync Cloud (hosted by us): See [Database Connection](/installation/database-connection#mongodb-alpha-specifics)
-   2. Using PowerSync Open Edition (self-hosted): Refer to our end-to-end demo app [available here](https://github.com/powersync-ja/self-host-demo/tree/main/demos/nodejs-mongodb)
+   1. **PowerSync Cloud**: See [Database Connection](/installation/database-connection#mongodb-alpha-specifics)
+   2. **Self-hosted**: Refer to our end-to-end demo app [available here](https://github.com/powersync-ja/self-host-demo/tree/main/demos/nodejs-mongodb)
 2. Define [Sync Rules](/usage/sync-rules) in PowerSync — this enables dynamic partial replication so that you don't need to sync your entire MongoDB database to devices.
    1. We recommend starting with one or two simple [Global Data](/usage/sync-rules/example-global-data) queries
 3. Generate a [Development Token](/installation/authentication-setup/development-tokens)
 4. Use our [Diagnostics App](https://diagnostics-app.powersync.com/) to validate that MongoDB is syncing into SQLite as expected.
-5. Implement an app using one of our Client SDKs
-   1. You can continue using your Development Token for a start
-   2. Implement a "Hello World" app to get a feel, **or** jump straight into pulling the Client SDK into your existing app.
-   3. Verify that downloads from MongoDB are working.
+5. Implement an app using one of our [Client SDKs](/client-sdk-references/introduction)
+   1. You can continue using your _Development Token_ for authentication as a start.
+   2. We recommend implementing a "Hello World" app to get a feel for how PowerSync works, _or_ you can jump straight into pulling the Client SDK into your existing app.
+   3. Verify that syncing from MongoDB is working.
 6. Implement [authentication](/installation/authentication-setup/custom)
-7. Implement your backend app to accept writes.
-   1. We have Node.js, Django and Rails demos available [here](/resources/demo-apps-example-projects#custom-backend-examples).
+7. Implement your backend app to accept writes. There are currently two options:
+   1. **Custom self-hosted backend:** If you already have a backend application as part of your stack, you should use your existing backend. Alternatively, we have Node.js, Django and Rails example implementations available [here](/resources/demo-apps-example-projects#custom-backend-examples).
+   2. **CloudCode hosted/managed backend:** An alternative option is to use CloudCode, a serverless cloud functions environment provided by us. We provide a template that you can use as a turnkey starting point. See our [documentation here](/usage/tools/cloudcode).
 
-### Implementation notes
+### Additional notes
 
 #### PowerSync Service
 
@@ -75,24 +75,28 @@ To [self-host](https://github.com/powersync-ja/powersync-service?tab=readme-ov-f
 
 #### PowerSync Client SDKs
 
-We are constantly adding additional PowerSync Client SDKs and some of them are under very active development. Below are the release status for each language/platform:
+We are constantly adding additional [PowerSync Client SDKs](/client-sdk-references/introduction) and some of them are under very active development. Below are the release status for each language/platform:
 
-| Flavor                                                              | Status      | ETA              |
+| Client SDK                                                          | Status      | Release ETA      |
 | ------------------------------------------------------------------- | ----------- | ---------------- |
 | [JavaScript/Web](/client-sdk-references/javascript-web)             | Stable      | N/A              |
-| [React Native](/client-sdk-references/react-native-and-expo) & Expo | Stable      | N/A              |
+| [React Native & Expo](/client-sdk-references/react-native-and-expo) | Stable      | N/A              |
 | [Flutter/Dart](/client-sdk-references/flutter)                      | Stable      | N/A              |
 | [Kotlin Multiplatform](/client-sdk-references/kotlin-multiplatform) | Beta        | V1 ETA 2025Q1    |
 | [Swift](/client-sdk-references/swift)                               | Beta        | V1 ETA 2025Q1    |
 | Node.js                                                             | PoC         | Alpha ETA 2025Q1 |
-| .NET                                                                | Not Started | Alpha ETA 2025Q1 |
+| .NET                                                                | In Progress | Alpha ETA 2025Q1 |
 
 <Info>
    We've had customers inquire about the availability of a Rust/C++ SDK. The PowerSync core SQLite extension is implemented in Rust and we can work with customers to integrate PowerSync into their C++ applications. Please reach out to us at hello@powersync.com or [schedule a call](https://www.powersync.com/contact) with us
 </Info>
 
 #### App Backend
 
-You will need to host a backend that can accept client writes if you do not already have one. The app backend needs to expose an API endpoint to write changes from the PowerSync client.
+Your app backend needs to expose an API endpoint to write changes from the PowerSync client to the backend MongoDB database.
+
+As noted above, there are currently two options:
+  1. **Custom self-hosted backend:** If you already have a backend application as part of your stack, you should use your existing backend. If you don't yet have one: We have Node.js, Django and Rails example implementations available [here](/resources/demo-apps-example-projects#custom-backend-examples).
+  2. **CloudCode hosted/managed backend:** An alternative option is to use CloudCode, a serverless cloud functions environment provided by us. We provide a template that you can use as a turnkey starting point. See our [documentation here](/usage/tools/cloudcode).
 
-Additional implementation notes are available [here](/installation/app-backend-setup/writing-client-changes).
+Additional backend implementation details are available here: [Writing Client Changes](/installation/app-backend-setup/writing-client-changes).