Aaron Boodman's banner

Aaron Boodman

@aboodman • 9,117 subscribers

CEO @rocicorp. Building @zero__ms, raising two great kids, trying to be a better person. Past: @replicache, @nomsdb, @googlechrome.

Videos

Anya Rossi

sweetdream.ai

SweetDream.ai•Sponsored•Livecam

Watch Anya Live

Anya is streaming live right now! Join her private show and enjoy exclusive content.

Exclusive private shows

1.2k viewers online

Private Show

Join now for exclusive access

Free preview available • Premium content

Introducing ztunes, a brand new Zero starter built on TANSTACK, Drizzle ORM,and Better Auth. Featuring: - Instant (0ms) navigation, mutations, and search - Significant dataset (100k artists from 1990's) - Personalization - < 1s LCP - Super elegant TanStack integration - Easy deployment to Fly.io Much more detail to share next week! But for now, check the live demo and GitHub in reply ↩️

68,036 Aufrufe • vor 11 Monaten

Sync engines enable instantly responsive UI. But the tradeoff is usually slow startup because all data must be pre-loaded. Zero's query-driven sync enables precise control over when data syncs. To demonstrate, we scaled our "zbugs" demo up to 2.5M rows. Introducing Gigabugs:

Sync engines enable instantly responsive UI. But the tradeoff is usually slow startup because all data must be pre-loaded. Zero's query-driven sync enables precise control over when data syncs. To demonstrate, we scaled our "zbugs" demo up to 2.5M rows. Introducing Gigabugs:

48,856 Aufrufe • vor 7 Monaten

IVM go brr. Darick is implementing a stress test of Zero's replication path. The script on the right is updating by writing directly to Postgres. This is replicating into zero-cache and syncing to the client.

IVM go brr. Darick is implementing a stress test of Zero's replication path. The script on the right is updating by writing directly to Postgres. This is replicating into zero-cache and syncing to the client.

33,283 Aufrufe • vor 1 Jahr

Supabase is now fully supported on Zero. Schema migrations happen automatically and efficiently. Thank you very much to the Supabase team for getting this shipped *and* for starting work to upsteam so other Postgres vendors can benefit. More information:

Supabase is now fully supported on Zero. Schema migrations happen automatically and efficiently. Thank you very much to the Supabase team for getting this shipped and for starting work to upsteam so other Postgres vendors can benefit. More information:

28,830 Aufrufe • vor 1 Jahr

Quick demo of Zero’s new background queries. Zero’s sync is query-based. Rather than specifying what data you want using rules or some other separate system, you just use queries. Right inside the client app, you do a query using a full sql-style language. You get filters, subqueries , limits, etc. Zero syncs the data backing these queries to the client. It’s important to realize Zero isn’t really a cache. It’s a replica. It’s eagerly replicating a precise snapshot of a slice of your database - the slice covered by the queries you have open. So there is never stale data in Zero. When you close a query we delete the rows uniquely returned by that query because we can no longer keep them up to date. Of course that kind of sucks for the common case of doing a query, navigating, then pressing “back”. Ideally we want that back nav to be fast. To address this Zero 0.17 adds background queries. You can add a ttl to a query and it will keep running and syncing in the background. This is much different than normal caching because this data stays up to date. If you make the same query again, the results will be *instantly* available *and already up to date with server*. If you make a different query the data from the background query is used client-side to answer the new query instantly if possible. This all happens completely automatically. Just by adding the ttl flag.

Quick demo of Zero’s new background queries. Zero’s sync is query-based. Rather than specifying what data you want using rules or some other separate system, you just use queries. Right inside the client app, you do a query using a full sql-style language. You get filters, subqueries , limits, etc. Zero syncs the data backing these queries to the client. It’s important to realize Zero isn’t really a cache. It’s a replica. It’s eagerly replicating a precise snapshot of a slice of your database - the slice covered by the queries you have open. So there is never stale data in Zero. When you close a query we delete the rows uniquely returned by that query because we can no longer keep them up to date. Of course that kind of sucks for the common case of doing a query, navigating, then pressing “back”. Ideally we want that back nav to be fast. To address this Zero 0.17 adds background queries. You can add a ttl to a query and it will keep running and syncing in the background. This is much different than normal caching because this data stays up to date. If you make the same query again, the results will be instantly available and already up to date with server. If you make a different query the data from the background query is used client-side to answer the new query instantly if possible. This all happens completely automatically. Just by adding the ttl flag.

18,808 Aufrufe • vor 1 Jahr

Keine weiteren Inhalte verfügbar