It isn't good but I doubt the UK punishment would be nearly as harsh or expensive and the possibility of death isn't on the menu when the cops come to arrest them.
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]
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.
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)
Systems-focused backend engineer with deep experience in databases, sync/state management, and production infrastructure.
Hands-on with SQLite, relational databases, replication-like workflows, and reliability under real-world constraints.
Long-term open-source contributor, comfortable owning complex backend systems end-to-end.
Not sure if you're open to using tools for this, but PowerSync solves those tricky things you listed (and many more you didn't list (disclaimer I'm on the team))
I’m mostly interested in the architectural side rather than a specific tool:
how people separate domain state from transport,
where optimistic state lives,
and how retry / reconciliation is usually modeled without leaking everywhere.
Still useful to see how existing systems approach client IDs though.
Cool, makes sense. We still want to write a blog post about how we built powersync that will go into more detail on the points you raised.
The one thing I'll add is we found "keeping UI responsive while syncing in the background" is highly platform dependent since all platforms have their quirks, but for React Native we have a detailed blog post and code (admittedly tightly coupled to powersync, but should provide a starting point) https://www.powersync.com/blog/keep-background-apps-fresh-wi...
Monero's main "competitor" seems to be Zcash which is run by a VC-backed company. The company gets 20% of all mined Zcash. The incentive is very strong to FUD Monero.
As of this comment, Monero is #26 on CoinGecko's list of crypto by marketcap with Zcash at #27. I'm guessing that's why there's a few of these posts on HN all of a sudden.
Sure, but I more meant people recycling year old news for clicks, and smart people falling for it. That's a very broad phenomenon and not tied to crypto.
PowerSync is a sync engine that keeps your backend database in sync with on-device SQLite. We support Postgres, MySQL and MongoDB 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
Our team is small and polyglot, but experience with TypeScript is a must.
If you're a database enthusiast and have a solid track record of building, deploying and maintaining backend systems on modern cloud stacks, you're already a candidate. Also, if you're passionate about open source and synced / local-first/offline-first apps, please apply.
Culture: We're agile and devops purists (before those terms got coopted)
We don't come up against them in deals, but I do believe it can be a replacement. I heard from a customer that SAP are planning to EOL MobiLink, have you heard the same?
reply