Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jodah
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
1.
▲
The AI Great Leap Forward
(leehanchung.github.io)
142 points
by
jodah
5mo ago
|
67 comments
2.
▲
by
jodah
8mo ago
This is excellent news if it can actually be enforced.
3.
▲
Failsafe-go – Adaptive concurrency limiting in Golang
(failsafe-go.dev)
6 points
by
jodah
1y ago
|
1 comments
4.
▲
by
jodah
2y ago
Author here - yes, Failsafe-go definitely took some inspiration from Polly, but it also borrows ideas from the Failsafe JVM library [1]. Polly and Failsafe influenced each other back and forth over the years. https://failsafe.dev
5.
▲
by
jodah
2y ago
Author here - I do get this critique, and of course API design is subjective, but there was a rationale behind the design choices. Putting each policy in its own package allowed the API to be slightly more concise. And having the API use a
6.
▲
by
jodah
3y ago
There are some (imperfect) workarounds, ex: https://github.com/jhalterman/typetools
7.
▲
Failsafe-go: resilience patterns for building fault-tolerant Go applications
(failsafe-go.dev)
15 points
by
jodah
3y ago
|
2 comments
8.
▲
by
jodah
3y ago
I would love to learn how Bob approached interviewing, if you've ever up to writing this up!
9.
▲
by
jodah
3y ago
While I didn't know Bob personally, he did he an impact on me. Bob was the first person I looked up to as an open source engineer early in my career. I studied his code closely, and learned a lot from the way he was able to distill com
10.
▲
Failsafe 2.0 released – Failure handling and resilience patterns for the JVM
(github.com)
2 points
by
jodah
8y ago
|
0 comments
11.
▲
by
jodah
9y ago
Atomix has a Jepsen test suite[1], which while not perfect, has helped fix the bugs that existed in the Raft implementation. 1: https://github.com/atomix/atomix-jepsen
12.
▲
by
jodah
9y ago
"For ILock, the lock is not mutually exclusive under split brain. However it can still be useful as an advisory lock." Why use a lock that isn't safe when there are other alternatives?
13.
▲
by
jodah
9y ago
For anyone wondering if there is a set of Hazelcast like data structures and primitives that actually have safe, strong consistency (based on Raft consensus), check out Atomix: http://atomix.io/atomix/
14.
▲
How to Create a Distributed Datastore in 10 Minutes
(jodah.net)
3 points
by
jodah
10y ago
|
0 comments
15.
▲
by
jodah
10y ago
12B sounds like an incredible number for labs. Is there a source?
16.
▲
Testing Multi-Threaded and Asynchronous Code in Java
(jodah.net)
3 points
by
jodah
10y ago
|
0 comments
17.
▲
by
jodah
10y ago
Good example of where random retry delays would be valuable. I filed this as a feature to add for the next release: https://github.com/jhalterman/failsafe/issues/39
18.
▲
by
jodah
10y ago
> Is there a more detailed comparison? There's nothing more detailed that I know of. Is there a particular feature area/comparison you're curious about? I can add a bit more detail. > It's not apparent to me what t
19.
▲
by
jodah
10y ago
Good question. Someone asked that recently on Github - here's a quick comparison: https://github.com/jhalterman/failsafe/wiki/Comparisons#fail...
20.
▲
by
jodah
10y ago
Author here: fully agree. Blindly retrying an operation any failed operation could lead to cascading failures or system overload, which is what circuit breakers are intended to avoid. Generally, it's just good to think about which fail
21.
▲
by
jodah
10y ago
Author here, Failsafe does support exponential backoffs [1]: retryPolicy.withBackoff(1, 30, TimeUnit.SECONDS); and if you want to specify the exponent [2]: retryPolicy.withBackoff(1, 30, TimeUnit.SECONDS, 1.5); As for which fa
22.
▲
Failsafe – failure handling with retries, circuit breakers and fallbacks
(github.com)
116 points
by
jodah
10y ago
|
41 comments
23.
▲
by
jodah
10y ago
Author here - We were aware of Maven Failsafe plugin (since we use it), but felt comfortable using the name anyways since Failsafe is an excellent description of what the library is about, it covers a different technical area than the Maven
24.
▲
Failsafe – A lightweight, zero-dependency library for handling failures
(github.com)
5 points
by
jodah
10y ago
|
0 comments
25.
▲
by
jodah
10y ago
> I have a debit card, I don't need to carry anything else. If your card hasn't been stolen (via a hacked merchant) and your account wiped out yet, consider yourself lucky. You might want to carry a credit card as your primary
26.
▲
by
jodah
10y ago
1 CPU still pegged on firefox. But otherwise, Reason looks very cool. A nice mashup of technologies to create something that certainly looks more useful than the status quo. I hope this takes off, but I think the biggest challenge nowadays,
27.
▲
by
jodah
10y ago
Incredible, but you are correct. Pegs 1 CPU in FF and while it loads, it barely scrolls.
28.
▲
by
jodah
11y ago
This, usually. It's fair to point out that very specialized clocks, such as Google uses with Spanner, can allow you to achieve some consistency without coordination/locks, but for pretty much anyone else the rule you stated very m
29.
▲
by
jodah
11y ago
I'm not sure that merely checking the result of some set of operations - whether a mutex is held by the expected process - tells you very much about the validity of how that mutex was obtained (assuming interleaving requests and such).
30.
▲
by
jodah
11y ago
> is certainly not sufficient to assume correctness of an implementation Indeed. This is where tools like Jepsen and good fuzz testing can help.
More ›