this post was submitted on 12 May 2024
617 points (92.2% liked)

Programmer Humor

19623 readers
2 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
617
Let's do micro service (sh.itjust.works)
submitted 6 months ago by alphacyberranger@sh.itjust.works to c/programmer_humor@programming.dev
78 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] lemmyvore@feddit.nl 1 points 6 months ago* (last edited 6 months ago)

I struggle to think of any code with real-world applications that doesn't have to make CAP tradeoffs. The reason that often doesn't seem to be the case is willful ignorance.

The only way you can have ACID in a monolith is if the data store is incorporated into the RAM when the code runs and the code is not interacting with any exterior system.

Typically the data store is external though and yes you can have atomic states in the data store but that doesn't translate to your code. That's CAP right there, between your code and your data running on two distinct systems.