Reuben Bond
@rbn.bsky.social
Distributed Systems & databases person. Works at Microsoft on Orleans & Aspire
I have an Aer one. You can get decent Tomtoc ones which mimic the designs of popular brands for less $ - unsure in the quality but I imagine they are decent.
August 31, 2025 at 11:11 PM
I have an Aer one. You can get decent Tomtoc ones which mimic the designs of popular brands for less $ - unsure in the quality but I imagine they are decent.
Async/await was a developer experience regression compared with blocking APIs, but a huge advancement over the APIs it replaced, which were callback based.
I'm optimistic about virtual threads as a best of both worlds, if we can retain the benefits of futures & structured concurrency
I'm optimistic about virtual threads as a best of both worlds, if we can retain the benefits of futures & structured concurrency
August 4, 2025 at 5:02 PM
Async/await was a developer experience regression compared with blocking APIs, but a huge advancement over the APIs it replaced, which were callback based.
I'm optimistic about virtual threads as a best of both worlds, if we can retain the benefits of futures & structured concurrency
I'm optimistic about virtual threads as a best of both worlds, if we can retain the benefits of futures & structured concurrency
Ah, thanks. How much of it is attributable to BEAM itself, I wonder. Using AOT instead of the JIT cuts memory usage in .NET by about half, for ex. IIRC, the numbers below are steady state under load, not startup, but either way
August 4, 2025 at 4:42 PM
Ah, thanks. How much of it is attributable to BEAM itself, I wonder. Using AOT instead of the JIT cuts memory usage in .NET by about half, for ex. IIRC, the numbers below are steady state under load, not startup, but either way
Thanks. Perhaps there is still low hanging fruit for elixir/phoenix/BEAM when it comes to reducing startup mem consumption. I'm sure it would still consume more than a Rust app given the nature of the runtimes
August 4, 2025 at 4:30 PM
Thanks. Perhaps there is still low hanging fruit for elixir/phoenix/BEAM when it comes to reducing startup mem consumption. I'm sure it would still consume more than a Rust app given the nature of the runtimes
Pat Helland delivered a presentation on this paper: hpts.ws/papers/2024/...
April 9, 2025 at 4:06 PM
Pat Helland delivered a presentation on this paper: hpts.ws/papers/2024/...
It's just a toy / proof-of-concept, really, but it might be useful to refer to.
March 3, 2025 at 5:51 PM
It's just a toy / proof-of-concept, really, but it might be useful to refer to.
Thank you, Jeremy! I gave a presentation about some of the design considerations in the serialization & RPC system: www.youtube.com/live/kgRag4E...
Reuben Bond - Orleans under the hood (Dotnetos Conference 2021)
YouTube video by Dotnetos
www.youtube.com
January 29, 2025 at 4:32 AM
Thank you, Jeremy! I gave a presentation about some of the design considerations in the serialization & RPC system: www.youtube.com/live/kgRag4E...
All things agents. I'm interested in builder communities rather than per-product servers
January 4, 2025 at 10:29 PM
All things agents. I'm interested in builder communities rather than per-product servers
Committing the first value is safe as-is, but by playing more with this I believe subsequent Fast Rounds require additional safety rules:
1. Proposers only propose updates to known-committed values
2. Acceptors require the value's version (akin to slot number) has increased or values are identical
1. Proposers only propose updates to known-committed values
2. Acceptors require the value's version (akin to slot number) has increased or values are identical
January 3, 2025 at 5:33 PM
Committing the first value is safe as-is, but by playing more with this I believe subsequent Fast Rounds require additional safety rules:
1. Proposers only propose updates to known-committed values
2. Acceptors require the value's version (akin to slot number) has increased or values are identical
1. Proposers only propose updates to known-committed values
2. Acceptors require the value's version (akin to slot number) has increased or values are identical
Did he have his onion juice with him or a couple of pocket eggs? If not, he's ngmi
January 3, 2025 at 7:18 AM
Did he have his onion juice with him or a couple of pocket eggs? If not, he's ngmi
gotta max out those T levels somehow
January 3, 2025 at 4:19 AM
gotta max out those T levels somehow
Is there a doc describing it?
December 15, 2024 at 6:54 PM
Is there a doc describing it?
"nothing more" is a bit too far: CRDTs have limitations on their behavior. You can't implement just anything using CRDTs. Their utility is quite limited and hence they are not widely deployed within datacenter based apps (I know of none, and no one has provided examples yet)
December 15, 2024 at 6:43 PM
"nothing more" is a bit too far: CRDTs have limitations on their behavior. You can't implement just anything using CRDTs. Their utility is quite limited and hence they are not widely deployed within datacenter based apps (I know of none, and no one has provided examples yet)
It depends on the CRDT, but that's not my area of expertise. The journaled grains use event sourcing (modified for geo distributed environments), and I believe you could implement CRDTs on top fairly easily, but the API also exposes coordination/sync operations for consistency.
December 15, 2024 at 6:01 PM
It depends on the CRDT, but that's not my area of expertise. The journaled grains use event sourcing (modified for geo distributed environments), and I believe you could implement CRDTs on top fairly easily, but the API also exposes coordination/sync operations for consistency.
What I described is not a CRDT. I am talking about ACID database transactions using optimistic concurrency control
December 15, 2024 at 5:10 PM
What I described is not a CRDT. I am talking about ACID database transactions using optimistic concurrency control
You can version the data and check for conflicts at commit time, similar to a database transaction with optimistic concurrency control.
December 15, 2024 at 4:48 PM
You can version the data and check for conflicts at commit time, similar to a database transaction with optimistic concurrency control.
In the online case you can coordinate changes. In the offline case you cannot: you have divergent data replicas being updated independently. The changes need to be merged eventually and there is ambiguity as to how.
December 15, 2024 at 4:41 PM
In the online case you can coordinate changes. In the offline case you cannot: you have divergent data replicas being updated independently. The changes need to be merged eventually and there is ambiguity as to how.
That's CRDT territory, but the goalposts just shifted
December 15, 2024 at 4:23 PM
That's CRDT territory, but the goalposts just shifted