undefined | Better HN

0 pointsinfogulch2mo ago0 comments

He mentions Litestream, maybe this also works for litestream read-only replicas which may be in completely different locations?

0 comments

3 comments · 1 top-level

russellthehippo2mo ago· 2 in thread

Whoa I really hadn’t considered this. Do a litestream read replica, trigger across machines with S3 as the broker essentially. But you’re still stuck with the litestream sync interval. Maybe interesting for cross server notify?

infogulchOP2mo ago

I guess the idea is to have all writes go through a central server with local read replicas for improved read perf. The default litestream sync interval is 1s. I bet many use-cases would be satisfied with a few seconds delay for cross-region notifications.

russellthehippo2mo ago

It's good for pubsub but not for claim/ack workflow unless you do If-None-Match CAS semantics on a separate filesystem which, actually, yeah that's probably fine. Feels heavy on S3 ops. But! you do save on inter-AZ networking, the Warpstream hypothesis.

1 more reply

j / k navigate · click thread line to collapse