The release of Zero 1.0, Rocicorp's stable web sync engine, marks a significant milestone in the development of web applications. This release comes after nearly two years of hard work, with over 50 releases and thousands of commits, showcasing the team's dedication to creating a robust and reliable solution. The major version bump is largely symbolic, indicating that the core functionality has remained intact throughout the development process.
One of the key features of Zero is its schema change hook, which detects publication changes on Supabase through COMMENT ON PUBLICATION statements. This addresses Supabase's lack of event trigger support for publications, providing a more comprehensive solution for managing database changes. Additionally, the release includes fixes for corrupted litestream restores, error handling during unhealthy change data capture, and addressing an IPCCHANNELCLOSED race condition during shutdown. These improvements enhance the overall stability and reliability of the engine.
Zero's architecture is designed to be a bring-your-own-database approach, where a zero-client library inside the app pairs with a zero-cache service to maintain a read-only replica of a Postgres database. Queries written in ZQL, Zero's streaming query engine, run against the local cache first, and matching results are returned in the next frame. Authoritative results sync from the server in the background, ensuring data integrity and synchronization. This approach, as noted by Aaron Boodman, is a strength as it prevents data corruption and allows teams to adopt Zero incrementally or move away from it easily.
However, the community's reaction to Zero has been a mix of positive feedback and cautious optimism. While developer experience is praised, some limitations have been identified. These include support for only Postgres, the lack of syncing for Postgres views, and the non-support for certain Postgres column types like array. Additionally, the client bundle size of 718 KB uncompressed (232 KB gzipped) and the absence of server-side rendering have been points of criticism. The question of whether stacking local stores, sync replicas, and source databases adds unnecessary complexity has also been raised.
Zero enters a competitive market alongside ElectricSQL, InstantDB, PowerSync, and Convex. Boodman suggests that developers seeking fully decentralized, end-to-end setups should consider Jazz. Server-side rendering, however, remains a future goal rather than a current feature.
Upgrading to Zero 1.0 is straightforward due to the lack of breaking changes. Teams can simply use the updated npm package: npm install @rocicorp/zero@1.0. For those transitioning from older builds, it is essential to review the per-version release notes and follow the schema deployment guidance to avoid downtime during migrations. This ensures a smooth transition to the latest version of Zero, solidifying its position as a powerful tool for web application development.
