A cynical take Ive heard before: replacing a power cable with a lithium ion rechargeable battery turns many devices into a quasi subscription service (you pay for a product but then must "renew your subscription" when the battery goes out).
Hi, this is a very cool product and I am planning a project that I think could use it.
The question I have tho: How do you take advantage of the gains from this if you still need one master strictly consistent db for writes?
Would a system design pattern to take advantage of fly.io be to have read only replicas on each geographic deploy or to only have region specific persistance? Apologies if this was already answered I read thru everything I saw. Thanks!
I know the show was on nearly 20 years ago but I only watched it 2 months ago for the first time :)