6 ms·

You realize that your product offers no transaction support due to the HTTP API right?

• otoolep 2y ago
  Transactions -- or the lack thereof -- have nothing to do with the consistency guarantees offered by rqlite. You may wish to read this: https://github.com/wildarch/jepsen.rqlite/blob/main/doc/blog.md https://github.com/wildarch/jepsen.rqlite/blob/main/doc/blog... rqlite -- to the best of my knowledge and as a result of extensive testing -- offers strict linearizability due to its use of the Raft protocol. Each write request to rqlite is atomic because it's encapsulated in a single Raft log entry -- this is distinct from the other form of transactions offered by rqlite[1], but that second form of transaction functionality has zero effect on the guarantees offered by Raft and rqlite (they are completely different things, operating at different levels in the design). If you know otherwise I'd very much like to know precisely why and how. [1] https://rqlite.io/docs/api/api/#transactions https://rqlite.io/docs/api/api/#transactions
  • protosam 2y ago
    I won't be following up further. I've shared all I have to share on this topic. On a personal level, I'm actually disappointed in how you take to critical feedback about your product and don't seem to be interested in understanding the problem domain you're developing for. https://gist.github.com/protosam/35880f46ed3f3e80a4e2ec47e6b60b2e https://gist.github.com/protosam/35880f46ed3f3e80a4e2ec47e6b...