HackerTrans
TopNewTrendsCommentsPastAskShowJobs

tlaverdure

no profile record

comments

tlaverdure
·8 miesięcy temu·discuss
Yeah not free if you definitely need IPv4. AWS has been adding a lot more IPv6 support to their services so hopefully the trend continues in AWS and the broader industry. You can probably get pretty far though if your app doesn't have hard requirements to communicate with IPv4 only hots.
tlaverdure
·8 miesięcy temu·discuss
Abolish NAT Gateways. Lean on gateway endpoints, egress only internet gateways with IPv6, and security groups to batten down the hatches. All free.
tlaverdure
·8 miesięcy temu·discuss
Yes, these are both important points. I didn't see any mention of SQLITE_BUSY in the blog post and wonder if that was never configured. Something that people miss quite often.
tlaverdure
·9 miesięcy temu·discuss
Thanks for sharing. I really enjoyed the breakdown, and great to see small tech companies helping each other out!
tlaverdure
·10 miesięcy temu·discuss
A lot of similarities but I believe Turso replicates data between nodes.

Litebase writes data to a tiered storage system (local, network, and object) for easier distribution. Using SQLite's VFS API I've also implemented a different type of storage that allows the primary to write data without full consensus with replicas. It's kind of like a multi-versioned log structured merge tree.
tlaverdure
·10 miesięcy temu·discuss
> Another implication of having just one single server: there is only one place for network requests to go.

> In the dream SQLite plus LiteFS world, you have all the advantages of SQLite and all the advantages of a fully replicated multi-writer database setup. Any individual server can go down without causing any downtime for the application as a whole, and every user has a full copy of the application and all its data, running extremely close to them.

These are some of the problems I’m working on solving with Litebase (alpha), which runs on SQLite and distributed storage. Most SQLite solutions rely on replicating data between nodes, but I’m taking a simpler approach by using distributed storage for durability, availability, and replication, combined with a lightweight consensus system between primary and replica nodes.

https://litebase.com

I’m working on getting a public alpha ready, but you can check out the project so far. I’ll create a thread on Hacker News once things are ready.