Programmer Humor

32495 readers

268 users here now

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

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

cat_programmer@lemmy.ml

436

neither will moving to the cloud (lemmy.cringecollective.io)

submitted 5 months ago by listless@lemmy.cringecollective.io to c/programmerhumor@lemmy.ml

42 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] justcallmelarry@lemmy.dbzer0.com 12 points 5 months ago (1 children)

Tbh mostly microservices solves two issues for me:

You can scale resource-heavy operations without an impact of scaling everything else.
You kind of ”force” people to keep things contained, instead of making everything interdependant. Which helps containing issues with updates to certain functionality to only have an impact on that functionality.

You could do #2 in a ”monolithic” setup as well (by doing modules or libraries or something), it just never works out that way in practice

[–] listless@lemmy.cringecollective.io 3 points 5 months ago (2 children)

Let's say there is a user lmicroservice. I'm on a UI team. I don't get to tell the user service team what, or when, to implement any features.

I'm tasked with making a page displaying all the users who have a birthday this month.

User API service can only search by user id, email, display name, or nickname.

Now instead of just querying the goddamn database, a one line fucking SQL statement, I have to deal with the user team, getting them to first off even admit that my use case is valid, convince them to work on the feature, coordinate with them to make sure the query works, sorts the data the way I need, etc, et. al, blah blah blah.

They already have the next 3 sprints full so I'm sitting on my ass for the next month before I can test.

Meanwhile they decide they're gonna implement a super generic thing, and so despite me working on code that we talked about using an interface we talked about, they implement something else so i have to throw out half my work anyway.

Then when I finally start using it I find, oh, it doesn't support a sort, only returns 100 results max with no pagination, so if there's 200 this month with a birthday fuck the 2nd hundred they don't show up because they're implementing bare minimum and the rest is slated for another sprint.

And it was then, your Honor, I grabbed the lead dev for the user microservice and tossed him off the 9th story of the building.

/sarcasm

[–] Akisamb@programming.dev 6 points 5 months ago

Now instead of just querying the goddamn database, a one line fucking SQL statement, I have to deal with the user team

Exactly, you understand very well the purpose of microservices. You can submit a patch if you need that feature now.

Funnily enough I'm the technical lead of the team that handles the user service in an insurance company.

Due to direct access to our data without consulting us, we're getting legal issues as people were using addresses to guess where people lived instead of using our endpoints.

I guess some people really hate the validation that service layers have.

[–] justcallmelarry@lemmy.dbzer0.com 3 points 5 months ago (1 children)

I know you wrote /s, but this has basically nothing to do with the tech of microservices, and more to do with internal politics.

Switch the ”user microservice” to ”birth date is not indexed in the database and i have to reach out to the database handling team” and you are in the same situation

[–] NigelFrobisher@aussie.zone 1 points 5 months ago

True, but the microservice concept was introduced to perform a kind of reverse-Conway Manoeuvre and make the architecture fit the team topology. Whether this has ever worked is still unclear to me, but I’ve seen it not work a few times now.