otoolep
Twelve years of distributed SQLite
(I'm not the OP)
Humanoid robots won't surprise us when they arrive
'Star Trek' Endures for the Next Generation, and the Next, and the Next
Taking Control of the SQLite WAL
Proving to Fable I maintain the repo
Data integrity in rqlite: what it checks and what it doesn't
Humanoid robots won't surprise us when they arrive
Taking Control of the SQLite WAL
The eerie abandoned vehicles in Chernobyl's 'dead zone'
How (and why) rqlite takes control of the SQLite Write-Ahead Log
One application that comes up over and over again -- wanting relational modeling, along with HA, but with low operational costs. People sometimes start with Postgres, then need to set up HA, and find it's a lot of work. They realize that their data set requirements are not huge, don't need fancy features, so start to think Postgres is overkill. That's what Replicated found.
Show HN: rqlite – the fault-tolerant DB built on SQLite – v10.0 released
https://github.com/rqlite/rqlite/releases/tag/v10.0.0
https://rqlite.ioMajor new release which improves clustering robustness, especially when dealing with slow Followers. New features include a built in web-based console (at localhost:4001/console) and comprehensive use of CRC32 for even strong data integrity guarantees. Lots of other bug fixes and improvements under the covers.Full list of changes at at...
In Europe the individual has almost no legal reason to use force, and force by individuals is considered illegitimate. The "Sovereign" has all the coercive power in European states. In the US, however, a certain amount of legitimate force explicitly remains with the individual i.e. the 2nd amendment. (I am not making a value judgement here).
Of course, Europe has government with the consent of the governed, so is Lockean in that sense. But the balance of force between the "Sovereign" and the people in Europe is all Hobbes. You only notice it when you move to the US and compare it to Europe.
Europe had centuries of religious and civil war. It's not surprising Hobbes won out.
Open Decision-Making (2021)
The source code was the moat. But not anymore
The Fall of the Nerds
As for reliability - it's a fault-tolerant, highly available system. Reliability is the reason it exists. :-) If you're asking about quality and test coverage, you might like to check out these resources:
- https://rqlite.io/docs/design/
Talking to LLMs has improved my thinking
This is the only part of your response that doesn't quite sit right with me. There could be many "highly scrutinized and bureaucratic functions" out there that are working very well, you just don't notice because they work so well. There could be a selection-effect here.
Quality is a big deal for me[1]. But I think you're defining "quality" too narrowly in this context. "Quality" could also mean "allows everyone, at scale, reliably, to do what they need to do." The US Tax Filing system (and its associated software) meets that goal.
[1] https://philipotoole.com/always-thinking-of-the-next-guy/
The Engineering Management Myths Star Trek Teaches (2022)
Common misunderstandings about large software companies
The liquid air alternative to fossil fuels
Otherwise, if you try with more modern networks and disks, let me know what you see.
I did introduce Queued Writes[1] since that talk, allowing you to trade off performance versus immediate durability. It may interest you -- network is much less of a factor then, and you should get a 10-100x increase in throughput.
Yes I do have practical experience to share, I wrote a blog post on rqlite and FTS5: https://philipotoole.com/building-a-highly-available-search-...
Will it allow you to reach the same scale in terms of data set size that Elasticsearch supports? Almost certainly no, but it might be enough depending on your use case.
- https://www.philipotoole.com/2021-rqlite-cmu-tech-talk - see slide 33.
- There is also a recording that goes with the talk: https://www.youtube.com/watch?v=JLlIAWjvHxM
You can also read about Performance in the docs at: https://rqlite.io/docs/guides/performance/
An important thing to note: this testing was done 4+ years ago, on moderately-powerful hardware for the time. With higher-end, more modern hardware you may get even better results.