Production-Ready MongoDB Sync Engine
We are excited to announce that PowerSync’s MongoDB Connector has advanced to Beta status. With this release, PowerSync is now ready for production use in both self-hosted and MongoDB Atlas environments, offering robust support under our commercial agreements, including premium support SLAs.
This release assures that MongoDB will remain a key database player in the evolving sync engine market. Sync engines simplify state management between databases and applications. They manage state transfer between the backend database and the app asynchronously in the background, freeing developers up from writing low-level data transfer plumbing logic: a tedious task fraught with technical complexity. This enables developers to focus on building valuable features for their customers.
Following our partnership announcement with MongoDB in October, we’ve collaborated extensively with their leadership, engineers, and sales teams to assist customers in preparing for the rapidly approaching Atlas Device Sync end-of-life in September 2025. We’ve also seen a steady influx of customers on our Discord server where our engineers assist with technical migrations.
Several MongoDB customers ranging from enterprises to startups have already selected PowerSync to replace Atlas Device Sync. Examples include UK package delivery service Yodel, POS solution KaHero, and dairy management system Ordenha Facil. PowerSync provides a range of engagement models and pricing plans to suit the needs of businesses of varying types and sizes, including self-service and enterprise options.
Consistency Guarantees For Synced Data
Many developers don’t realize the importance of consistency guarantees when it comes to distributed state management. Consistency issues are notoriously difficult to diagnose and debug and even though consistency may not be an issue from the outset, it can become a huge pain for serious deployments. This is why we prioritized providing rock-solid causal consistency guarantees for our Beta release. This is important for any use cases where ordering of any type is required to make sense of the data or interpret the state.
After consulting with the Atlas Device Sync architecture team, we adopted a similar approach to Atlas Device Sync of using [.inline-code-snippet]changeStreamPreAndPostImages[.inline-code-snippet] to guarantee casual consistency. In addition to automatically configuring this for synced collections, we also provide manual configuration options for environments with stricter security requirements.
Flexibility of CRUD Uploads
A significant architectural advantage of PowerSync over the soon-to-be-discontinued Atlas Device Sync is the enhanced control it offers developers over the handling of local mutations and their processing into MongoDB. By default, the PowerSync client SDK queues and sends local mutations to the developer’s backend API, so that custom business logic and/or validations can be applied before writing the changes to MongoDB. As an alternative to running their own backend API, some customers are using the customizable serverless CloudCode environment provided by PowerSync to host these write endpoints. Contact us for more information on this option.
Roadmap to V1
See the Beta release notes for more information on what we worked on to get from Alpha to Beta.
As we progress towards Version 1, our roadmap remains adaptable, guided by customer feedback. Our focus includes enhancing usability, improving documentation, 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.
Using PowerSync
Begin your journey with PowerSync by signing up for a free PowerSync Cloud account here. PowerSync can also be fully self-hosted in your own environment, and our MongoDB self-host-demo app is a good place to get a feel for the system.
Appendix: Client SDK Release Status
PowerSync supports a wide range of client SDKs and frameworks. The release status of various SDKs at the time of writing is summarized below
