HN user

kobieps

168 karma

creating powersync

Posts9
Comments86
View on HN

Not at all (hence saying "obvious in hindsight"). Simply pointing out that, at the time, my purchasing decision wasn't influenced by how many use cases it would restrict.

Also, IIRC, there was a period where you could burn Audio CDs from music that you purchased on iTunes.

edit: turns out music purchased on iTunes is DRM-free!

A recent experience I had was :

1. buy movie on iTunes 2. have kids that can't do long distance drives 3. obtain dvd players for car 4. realized I can't play films that I "bought" on DVD players

It feels like the "Buy" button on iTunes/Apple TV is misleading, and should be renamed to "License to watch on Apple devices". Obvious in hindsight, but this type of DRM severely restricts use cases.

I spend a lot of time in wilderness areas that I don't know, and I simply pull my phone out of my pocket to see where I am. My watch measures my heart rate and that's it. While I have no doubt that pedometer++ is great and the work that went into it is impressive, I can't really see myself switching away from a big screen workflow to see exactly where I am. And I don't need to check where I am every 5 minutes. Typically only every 30 minutes or longer. Dunno, maybe I'm missing something :shrug:

GPT-5.5 3 months ago

Balaji's "AI OVERPRODUCTION" post is the most compelling thesis that I've come across

No it's a full story, more akin to zero (at the highest level that is, many many differences and trade-offs).

Unfortunately I'm not qualified to answer that last question... I'm on the PowerSync team. What I can say is that we get a lot of praise from users (the ones that survive onboarding that is, lots of DX improvements we still need to make)

I suppose the only part the OP would need to look at is "Being able to form and execute queries in my backend" for the read path, since Sync Rules / Sync Streams need to define those queries. For the write path, you should be able to re-use the existing APIs / permission middleware for the most part.

Then: "Further, I wonder how such a system would work with connection pooling, sharding, replication etc."

These are all topics on their own, but briefly: - Connection Pooling: Not supported in PowerSync Cloud atm, but supported in theory when self-hosting since pgbouncer 1.23 added WAL support. Having said that, clients connect to the PowerSync Service for sync operations, so you only need a single direct connection between the service and your postgres. - Sharding: PowerSync can be used in a sharded setup [1], with better support planned - Replication: PowerSync uses the Postgres WAL for replication [2]

[1] https://docs.powersync.com/usage/sync-rules/advanced-topics/... [2] https://docs.powersync.com/installation/database-setup#other...

PowerSync | Senior Backend Engineer and Database Expert | Full-time | Remote (opt-in regional offices)

PowerSync is a sync engine that keeps your backend database in sync with on-device SQLite. We support Postgres, MySQL, MongoDB and SQL Server as source databases and have a plethora of client SDKS, many of which are integrated with popular libraries and frameworks on the client-side like TanStack DB, Drizzle, GRDB, Room, etc

If you're a database enthusiast and have a solid track record of building, deploying and maintaining backend systems on modern cloud stacks at scale, please check us out.

Detail: https://www.powersync.com/careers/senior-backend-engineer-an...

Our team is small and polyglot, but experience with TypeScript is a must.

Experience with OSS projects is also a must - either you've made significant contributions to popular devtool projects or, better yet, you have your own.

Culture: We're agile and devops purists (before those terms got coopted)