this post was submitted on 12 May 2024
185 points (90.7% liked)

Programmer Humor

32483 readers
302 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] PeriodicallyPedantic@lemmy.ca 15 points 6 months ago (1 children)

IMO there are two underrated benefits:

  1. It enforces separation of concerns
  2. It provides options to OPS.

Designing for micro services doesn't mean you need to deploy it as micro services. You can deploy it as a monolith and configure it too skip the network stack

[–] yogthos@lemmy.ml 3 points 6 months ago (1 children)

I very much agree with designing things in style of microservices in terms of having isolated components that can be reasoned about independently. In my experience, this is the only way to keep large projects manageable. Incidentally, this is also why I've come to appreciate functional approach with immutability as the default. It makes it much easier to write largely stateless code where all the IO happens at the edges, and then you just pass your context around explicitly through pure functions.

[–] PeriodicallyPedantic@lemmy.ca 2 points 6 months ago

A coder after my own heart. State machines are the bane of my existence.