Introducing Postgres for Sync Bucket Storage (Open Edition and Enterprise Self-Hosted)

We’re excited to announce Postgres for sync bucket storage, introduced in version 1.3.8 of the PowerSync Service image. This feature provides developers who self-host PowerSync with the flexibility to use Postgres as a storage backend for sync buckets, alongside the existing MongoDB option.

Why Postgres Sync Bucket Storage?

Until now, PowerSync has relied on MongoDB for sync bucket storage. While MongoDB remains a powerful choice, we’ve heard from teams that use Postgres as their source database for PowerSync that they’d prefer to consolidate their infrastructure. With Postgres sync bucket storage, you can:

• Leverage Familiar Tools: Use the database system your team is already comfortable with.

• Reuse Existing Infrastructure: Integrate PowerSync with your current Postgres setup instead of provisioning entirely new cloud infrastructure for MongoDB Atlas. This could also reduce infrastructure costs.

• Simplify Vendor Management: Avoid the need to secure approval for new vendors like MongoDB Atlas or the complexity of self-hosting a MongoDB cluster.

Getting Started

To use Postgres for sync bucket storage, you’ll need to:

1. Update your PowerSync Service to version 1.3.8 or later.

2. Configure your Postgres storage database as described in our self-hosting documentation here.

3. Specify Postgres as the storage backend in your PowerSync Service config.

For an example implementation of the above, check out our demo app here.

Feature Status

Postgres sync bucket storage is currently in a Beta release. In PowerSync terminology, Beta means the feature is production-ready, provided you've adequately tested your use case. Functionality and performance should be on par with the MongoDB storage option.

Help and Feedback

If you need any help getting started or have any questions, chat with us on Discord. We'd also love to hear your feedback