home.social

#rqlite — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #rqlite, aggregated by home.social.

  1. @polarcoder Nice article, but it's aged a bit. #LiteFS and #rqlite are doing some really interesting things with distributed SQLite. I wrote up an article about LiteFS (using Go, but usable in all languages) if you're curious. 😊 golang.dk/articles/distributed

  2. @polarcoder Nice article, but it's aged a bit. #LiteFS and #rqlite are doing some really interesting things with distributed SQLite. I wrote up an article about LiteFS (using Go, but usable in all languages) if you're curious. 😊 golang.dk/articles/distributed

  3. @polarcoder Nice article, but it's aged a bit. and are doing some really interesting things with distributed SQLite. I wrote up an article about LiteFS (using Go, but usable in all languages) if you're curious. 😊 golang.dk/articles/distributed

  4. @polarcoder Nice article, but it's aged a bit. #LiteFS and #rqlite are doing some really interesting things with distributed SQLite. I wrote up an article about LiteFS (using Go, but usable in all languages) if you're curious. 😊 golang.dk/articles/distributed

  5. @polarcoder Nice article, but it's aged a bit. #LiteFS and #rqlite are doing some really interesting things with distributed SQLite. I wrote up an article about LiteFS (using Go, but usable in all languages) if you're curious. 😊 golang.dk/articles/distributed

  6. @serge The Litestream website has a nice overview of similar alternatives: litestream.io/alternatives/

    Quite nice selection for various priorities and trade-offs.

    TL;DR:
    - is primarily for disaster recovery
    - is a distributed file system from the same authors for "high availability and low global latency"
    - (and ) "trades higher durability for lower write throughput"

  7. @serge The Litestream website has a nice overview of similar alternatives: litestream.io/alternatives/

    Quite nice selection for various priorities and trade-offs.

    TL;DR:
    - #Litestream is primarily for disaster recovery
    - #LiteFS is a distributed file system from the same authors for "high availability and low global latency"
    - #rqlite (and #dqlite) "trades higher durability for lower write throughput"

  8. @serge The Litestream website has a nice overview of similar alternatives: litestream.io/alternatives/

    Quite nice selection for various priorities and trade-offs.

    TL;DR:
    - #Litestream is primarily for disaster recovery
    - #LiteFS is a distributed file system from the same authors for "high availability and low global latency"
    - #rqlite (and #dqlite) " trades higher durability for lower write throughput"

  9. @serge The Litestream website has a nice overview of similar alternatives: litestream.io/alternatives/

    Quite nice selection for various priorities and trade-offs.

    TL;DR:
    - #Litestream is primarily for disaster recovery
    - #LiteFS is a distributed file system from the same authors for "high availability and low global latency"
    - #rqlite (and #dqlite) " trades higher durability for lower write throughput"

  10. @serge The Litestream website has a nice overview of similar alternatives: litestream.io/alternatives/

    Quite nice selection for various priorities and trade-offs.

    TL;DR:
    - #Litestream is primarily for disaster recovery
    - #LiteFS is a distributed file system from the same authors for "high availability and low global latency"
    - #rqlite (and #dqlite) " trades higher durability for lower write throughput"

  11. Ooh, #rqlite looks like an interesting #PostgreSQL alternative for #Strolch. I'll need to write new DAOs, and then test to see how it works out... Got this from philipotoole.com/replicated-po

  12. Mit Version 7.0 führt das auf SQLite basierte rqlite unter anderem eine neue Node-Discovery-Integration mit Consul und etcd ein.
    rqlite 7.0: Verteilte Datenbanken mit Auto-Clustering einfacher managen