lknuth

I hve just implemented this after we moved away from SuperTokens. My takeaway is that its easier than you'd think (there are libraries that do interaction with the SSO provider for you) and you can fine tune it to your liking (for example, more involved account linking).

If you're starting out though, probably go for a SaaS in the beginning. But be sure to have monitoring for pricing and an option to close account creation, these things can become expensive fast.

I would love to see this become the [Litestream](https://litestream.io/) equivalent to SQLite: a very cheap option for simple deployments (ones with a single database) to get continuous backups in a cheap storage from which one can restore when needed.

My specific use-case would be: Single Postgres in my cluster, replicated via something based on pg_replicate running as a side-car and writing to my NAS running Minio.

I see what you mean. For my case, the network is much simpler. I'm also fine if an unavailable replication target means I can't start an application.

The upside of my solution is that there is no scheduling requirement on which node the PVC was initially created. There is also a certain guarantee that I have a working, recent backup of the application data. Starting from scratch every time is also basically a backup recovery operation. It gives me confidence that there is a recent backup which is restorable.

I'm not sure I understand your second point. Yes, if the external replication target is unavailable, I can't bring my local service back online. Same goes for if the replication target becomes unavailable and I don't realize it, there is potential for a lot of data to be lost if the application restarts.

For my personal usecase this is fine. I also have monitoring setup to look for just this case. It's a tradeoff between resilience and simplicity that works for some use cases - mine included.

I've leaned into it: all application state is on ephemeral storage and its constantly replicated "off-site" to a NAS running minio.

To accomplish this, I have restricted myself to SQLite as storage and use Litestream for replication. On start, Litestream reconstructs the last known state before the application starts. [Source](https://github.com/LukasKnuth/homeserver/blob/912cbc0111e44d...)

It works very well for my workloads (user interaction driven web apps) but there are theoretical situations in which data loss can occurr.

This perhaps? https://application.security/free/owasp-top-10

No, that doesn't exist. I'm also not sure if this is what they went to support.

I usually use Firefox Sync to send myself tabs.

This is really more like AirDrop, where Syncthing is more like DropBox.

Not to say they have no overlap, I use both. LocalSend is nice to quickly send that one picture from my Android to my MacBook