otoolep

35 ms·

421.
Jimmy Carter and the failures of management(philipotoole.com)
1 points by otoolep 8y ago|0 comments
422.
Finally, the Self-Driving Car(theatlantic.com)
3 points by otoolep 8y ago|0 comments
423.
GCP Stackdriver tips and tricks: Understanding metrics and building charts(cloud.google.com)
2 points by otoolep 8y ago|0 comments
424.
Jimmy Carter and the failures of management(philipotoole.com)
4 points by otoolep 8y ago|0 comments
425.
by otoolep 8y ago
Congrats to the team at Pachyderm!
426.
Metrics, tracing, and logging (2017)(peter.bourgon.org)
2 points by otoolep 8y ago|0 comments
427.
The gradual decline of the fade-out in popular music (2014)(slate.com)
33 points by otoolep 8y ago|47 comments
428.
General Relativity explained like you've never seen before(vis.sciencemag.org)
4 points by otoolep 8y ago|0 comments
429.
Simpson's paradox(en.wikipedia.org)
1 points by otoolep 8y ago|1 comments
430.
Atomic Commit in SQLite(sqlite.org)
2 points by otoolep 9y ago|0 comments
431.
by otoolep 9y ago
Rereading this, I see what you mean in the sense that if dealing == "fixing the fault", but tolerating == "keep going in the face of faults". So yes, you are right -- Raft doesn't fix the faults. One must still fi
432.
by otoolep 9y ago
>Well, if you’re being smart - do please tell us how Raft solves the problem of online faulty node replacement: I never said that it did. That is what I mean by my statement that more work is required to build a real system in the real w
433.
by otoolep 9y ago
> Raft doesn't deal with the faults I'm not sure what this means. The Raft paper explicitly states that Raft is a fault-tolerant system -- and by definition this means it deals with faults. To quote the paper: "Replicated
434.
by otoolep 9y ago
> What this project (and similar projects such as rqlite) doesn't address is the hard problem -- sharding. Yes, this is technically correct. However to meet its goals rqlite (and dqlites) does not require sharding. The point of rqli
435.
by otoolep 9y ago
rqlite is also a full application, whereas dqlite is more like the SQLite library -- you must wrap an application layer around it. In principle rqlite could use dqlite.
436.
by otoolep 9y ago
I don't agree. The whole point of putting a solid Raft implementation at the center of your system is deal with the faults. I myself built a simple distributed state machine which deals with faults perfectly well. Of course I built on
437.
by otoolep 9y ago
rqlite author here. I am considering adding distributed transaction support to rqlite (it already has a form of transaction support), if I can come up with a solid implementation, while keeping rqlite simple to deploy and operate (which i
438.
The Rise of Worse Is Better (1991)(dreamsongs.com)
55 points by otoolep 9y ago|44 comments
439.
The sad, gradual decline of the fade-out in popular music (2014)(slate.com)
2 points by otoolep 9y ago|0 comments
440.
The case against ORMs(korban.net)
1 points by otoolep 9y ago|0 comments
441.
A shared codebase does not a software team make(philipotoole.com)
5 points by otoolep 9y ago|0 comments
442.
Silicon Valley Is Not Your Friend(nytimes.com)
275 points by otoolep 9y ago|207 comments
443.
Distributed algorithms in NoSQL databases(highlyscalable.wordpress.com)
97 points by otoolep 9y ago|12 comments
444.
Why is it so hard to swat a fly?(bbc.com)
2 points by otoolep 9y ago|0 comments
445.
How the GIF won the Internet(bbc.com)
1 points by otoolep 9y ago|0 comments
446.
Show HN: Java client for rqlite, the lightweight distributed relational database(github.com)
2 points by otoolep 9y ago|0 comments
447.
Show HN: JavaScript client for rqlite, the distributed database built on SQLite(github.com)
2 points by otoolep 9y ago|0 comments
448.
Dear PMs, It's Time to Rethink Agile at Enterprise Startups(firstround.com)
1 points by otoolep 9y ago|0 comments
449.
by otoolep 9y ago
rqlite has the same limitations as SQLite in this regard.
450.
by otoolep 9y ago
Exactly.

More ›