68
submitted 9 months ago by [email protected] to c/[email protected]

I hear Sam Newman's - Monoliths to Microservices is worth a read.

top 10 comments
sorted by: hot top controversial new old
[-] [email protected] 10 points 9 months ago

Wasn't everyone here up in arms against micro services a week ago or so?

Just curious what everybody thinks.

[-] [email protected] 9 points 9 months ago

I've been out for a bit, what's wrong with them? Or is this being mixed up with microtransactions?

[-] [email protected] 11 points 9 months ago

Nah, there have been some blogs recently from engineers who were bucking the Microservice trend - Notably Amazon Prime Video moved back to more of a monolith deployment and saw performance improvement and infrastructure cost reduction

https://www.linkedin.com/pulse/shift-back-monolithic-architecture-why-some-big-making-boudy-de-geer

I wouldn't say anything is wrong with them, the pros and cons have been there, but the cons are starting to be more recognized by decision makers

[-] [email protected] 1 points 9 months ago

Ahh, thanks for the info!

[-] [email protected] 1 points 9 months ago

I mean, Prime Video is still a bunch of microservices, it comes down to where you define the boundary between 'service and 'microservice'. That blogpost was specifically about "the Prime Video audio/video monitoring service". Eg it's a service/microservice for QA, not for all of Prime Video. I'm sure there are seperate services for billing, browsing, captioning, and streaming.

And although the author called it "moving from microservices to monolith" it's more about moving from serverless to more traditional compute.

[-] [email protected] 5 points 9 months ago

They mainly make sense if you have insane amounts of traffic and/or are a giant company with a lot of independent teams.

For most companies using microservices, these are not true.

[-] [email protected] 2 points 9 months ago

They also make sense if you have heavily uneven traffic, either time-wise, service-wise, or both. Being able to scale up/down individual components is the point

[-] [email protected] 8 points 9 months ago

People make microservices way too small sometimes. Then you have the opposite problem with people trying to cram everything into one system. You need to recognize when some functions are related and should go together, or when something has a weird dependency and should just be separate.

[-] [email protected] 6 points 9 months ago

@xilliah @dandelion afaik microservices are fine. Just like a monolith can be fine. Maybe it just depends what you are sick of working with. :D

[-] [email protected] 4 points 9 months ago

Ah, the animal computer books of my childhood, lol.

My parents (both in tech fields) had a library of these before they split up.

Somehow I wound up in IT as a career, no one saw that coming, I assure you /s

this post was submitted on 17 Sep 2023
68 points (100.0% liked)

Programming

13266 readers
7 users here now

All things programming and coding related. Subcommunity of Technology.


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 1 year ago
MODERATORS