MongoDB as a Backend Database - Now in V1!

Today we are announcing the Version 1.0 release of our MongoDB Connector!

V1 marks a major milestone, delivering greater stability, performance optimizations, and enhanced functionality. This release has been shaped by working closely with MongoDB customers in both self-hosted and Atlas environments over the past few months.

If you’re new to MongoDB support in PowerSync, check out this blog post to learn how PowerSync offers a compelling alternative to Atlas Device Sync.

Key Updates in V1

In addition to a variety of bug fixes and stability improvements, these are the key updates we shipped to get to V1:

• Private Endpoints: Support for Atlas VPC/Private Endpoints is now available for customers on our Team and Enterprise plans.

• Performance: Optimized initial replication performance for documents by avoiding sessions (see the PR).

• Replication Progress Logging: Introduced progress logs for initial replication - these enable duration estimates in scenarios such as sync rule updates. Visit your Instance Logs (PowerSync Cloud) or see your replication service logs (self-hosted).

• Improved Support for Atlas Flex Instances: Collections could previously be truncated under specific conditions.

• Connection Settings in the Dashboard: MongoDB connection details now synchronize individual fields (username, hostname, database) with the URI field for better usability and consistency.

• Improved Change Stream Handling: Added support for MongoDB resume tokens, enhancing replication reliability by allowing the system to resume change streams from the last known state after interruptions (see the PR).

• Documentation Updates: We've expanded our documentation to address known gaps and improve clarity.

Get Started Today

Existing Users:

• V1 of the MongoDB Connector has been rolled out to all PowerSync Cloud instances. Additionally, we recommend switching to the Stable channel of the PowerSync Service for continued reliability.

• If you are using our Open Edition or Enterprise Self-Hosted Edition (self-hosted PowerSync deployments), simply update to the latest version of the PowerSync Docker image:

  docker pull journeyapps/powersync-service:latest

  There are no breaking changes, so you can upgrade confidently!

New Users:

• If you are migrating from Atlas Device Sync, see our migration guide.

• PowerSync Cloud: Sign up at powersync.com, create a PowerSync instance, and select "MongoDB" as your connection type.

• Open Edition or Enterprise Self-Hosted Edition: Follow our self-hosting guide to get started and ensure you are on the latest version of the PowerSync Service.

Need Help, Have Feedback?

Join the conversation on Discord. As always, we welcome your feedback!