why couldn't LiteFS just observe writes to .wal and propagate only those like you are doing at Turso? Also ... if I understood correctly the primary is location based so you'll have fast primary in Europe, as example, but writings from US will inevitably need to end up there first, right? I think this is also common for other DBs, but I just would like to be confirmed reads are always fast (once in each replica) but writes are also "primary location latency" based. Is this correct? Last, but not least, please don't talk trash on JS, it's pretty awesome after all :P
the initial story about how turso was started was awesome!
why couldn't LiteFS just observe writes to .wal and propagate only those like you are doing at Turso? Also ... if I understood correctly the primary is location based so you'll have fast primary in Europe, as example, but writings from US will inevitably need to end up there first, right? I think this is also common for other DBs, but I just would like to be confirmed reads are always fast (once in each replica) but writes are also "primary location latency" based. Is this correct? Last, but not least, please don't talk trash on JS, it's pretty awesome after all :P
Great interview!