3 ms·
> What people actually wanted to talk about, though? Databases. And they completely avoid discussing it again in this article. It would be nice if I could kno
by kayodelycaon 3y ago
> What people actually wanted to talk about, though? Databases.
And they completely avoid discussing it again in this article.
It would be nice if I could know what their product is for because it doesn't seem to be the apps I work on.
- dementik 3y agoI presume they start discussing about it when LiteFS is matured enough.
- bryanlarsen 3y agoThis is a "raised money" post. So presumably they raised money so they can have a database answer in the future.
- tptacek 3y agoWe have a multi-region single-write-leader Postgres offering now, but "databases" means lots of things to lots of people, and the platform strategy is to build durable storage primitives that work for as many different databases as possible. People run things like Cockroach here, and edge deployment also makes SQLite especially interesting.
- tylergetsay 3y agoDo you have any info about how edge deployments + sqlite work and what kind of applications they are limited to?
- mrkurt 3y agoBasically, LiteFS: https://github.com/superfly/litefs https://github.com/superfly/litefs And then some load balancer cleverness that reroutes writes to a specific VM: https://fly.io/blog/globally-distributed-postgres/ https://fly.io/blog/globally-distributed-postgres/
- PKop 3y agoAny plans to port fly_postgres_elixir to sqlite to enable using this feature easily with with Elixir? I think your company building out developer tools to help use your platform would aid greatly in adoption...seems a necessity really, particularly addressing the pain-point of accessing data close to users.
- oneneptune 3y agoa bit off topic, but a big struggle that is growing related to data and databases; managing data residency. I've not found an easy way to handle this and countries seem to be passing more and more laws... it's tough for global applications!