Why I Built Litestream
litestream.io
Why I Built Litestream
1–10 of 178 posts
Re: Why I Built Litestream
#2I'm appreciating this because I'm seeing the value of single process and single machine workflows. And this is after spending a decade on massive scale distributed systems, so I know that 98% of all people don't need scale.
My bet is on a single document server, and I'm writing a programming language for board games : http://www.adama-lang.org/docs/what-the-living-document
While I do see a future of the concepts I espouse as I'm making the language feel like an excel-reactive environment, my focus is on having fun. This year looks to be a slow year for the language as I built up some UIs for games.
Litestreem looks very interesting because it may be the missing piece where I could leverage it to get durability of a single database.
Re: Why I Built Litestream
#3I'm appreciating this because I'm seeing the value of single process and single machine workflows. And this is after spending a decade on massive scale distributed systems, so I know that 98% of all people don't need scale. My bet is on a single document server, and I'm writing a programming language for board games : http://www.adama-lang.org/docs/what-the-living-document While I do see a future of the concepts I es…
My work over the last decade has also been in distributed systems and I completely agree most people don't need that scale. These new massive scale solutions are exciting for the few large companies that need them but it feels like everyone is being pushed onto these platforms as well—whether it makes sense or not.
Let me know if you end up giving Litestream a try and how it works for you. I'm really working to make the developer experience as easy as possible and I'd love to hear feedback.
Re: Why I Built Litestream
#4I think the simplicity of different thinking of this project is brilliant! Great work!
Having dealt with complicated db replication this sounds like a good fresh idea.
Re: Why I Built Litestream
#5Refreshing to see Ben and good luck with the new project. I'm a huge fan of boltdb and use it in micro. With a background in distributed systems also I share this frustration with the complexity of software and the direction cloud is taking in general. While my personal take is running things on a VPS, my work is all around platforms and I think the end user experience needs to be drastically simpler.
Re: Why I Built Litestream
#6Ben - What are some practical examples of use cases you see here over the long term?
Re: Why I Built Litestream
#7SQLite should be fine if your workload biased towards reads. But its design does prevent many-writers and these, even operates on completely different tables, has to be serialized between each other. This can be more problematic since many SQLite articles recommend big transactions to improve performance. And write transactions have to be serialized between each other. If you are a write-heavy workload, at some point, you may need to shard and may even need to implement custom transaction support on top of that yourself (or is there open-source libraries does that? rqlite from my understanding only handles consensus / replication, doesn't do sharding).
Re: Why I Built Litestream
#8Hi Ben, thank you so much for building this!
I'm currently working on implementing a set of data structures (and more things later) on top of SQLite (https://github.com/litements/) for some of the same reasons you mention in the article.
I probably don't even have 1/10 of your experience, but your work is really motivating me to keep working on it, thanks!
Re: Why I Built Litestream
#9> Solutions such as Kubernetes tout the benefits of zero-downtime deployments
To be fair, these features of k8s are nice to have. Is there a similar tool for running single node (i.e. ec2) instances that offers zero-downtime deploys? One way you could do it is run a EKS cluster with a single ec2 node running your single-node setup. You could get the benefits of k8s while still running the simple single-node arch
Re: Why I Built Litestream
#10Ben, regardless of the product (I have not checked it out yet), kudos on the pitch. At least for me it sounded genuine, and hit a few sore spots right in the stomach as it should.
Best of luck.