Seems to overlap well with @swardley.bsky.social 's evolution axis?

here's my short guide to concurrency

(a) don't do it
(b) ok, do the embarrassingly parallel stuff
(c) you can just use one big lock instead of writing async code
(d) global mutable state? sounds like you need a database
(e) fine grained locks? you are writing a specialised database, read a textbook

Isn't that it goes 1, 2, then back to 1 that's problematic? 1, 2, 2 would be easier to deal with

Thanks! Duplicates are okay, it's relatively easy to make processing idempotent. But out of order... :/

Scenario:
1. Publish lsn 1
2. Publish lsn 2
3. Crash (before flushing offset)
4. Read offset
5. Publish lsn 1 and 2 again

The topic now contains 1, 2, 1, 2

What am I missing?

Mockito is maybe close to this: github.com/mockito/mock... Every commit is released but as a snapshot. Once a month ish they publish a release version.

I can't control the world around me, but I can define the person I want to be, and how I contribute to making the world a better place.

I'll spend my days doing that work with intentionality.

👋