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

Programmer Humor

19589 readers
510 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
[–] agressivelyPassive@feddit.de 12 points 6 months ago (1 children)

I still have to find a name for this disease, but it's somewhat like "you're neither Google nor Netflix".

Everything has to be Scalable™ even if a raspberry pi could serve 200 times your highest load.

I'm currently involved with a "micro service system", that has very clear, legal requirements, so we know exactly, how much load to expect. At most, a few thousand users, never more than 100 working at the same time on very simple business objects. Complex business logic, but technically almost trivial. But we have to use a super distributed architecture for scalability....

[–] lemmyvore@feddit.nl 1 points 6 months ago (1 children)

I'm guessing you already got an answer for that though when you asked about it.

Could be either "oh you're right let's not do that", or "because we want to design for horizontal scalability rather than vertical in case the demand grows later", or "the client has requested and it's paying for this feature" and so on.

[–] agressivelyPassive@feddit.de 2 points 6 months ago

It's because they think it's what you're doing for a large project. Simple as that. There's no future demand, the client doesn't care, and I'm not right because they said so.