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

12 points

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

Just curious what everybody thinks.

permalink
report
reply
11 points

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

permalink
report
parent
reply
13 points

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

permalink
report
parent
reply
3 points

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.

permalink
report
parent
reply
2 points

Ahh, thanks for the info!

permalink
report
parent
reply
2 points

The Prime Video example was more like moving from nano-service insanity to sanity. They basically split EVERY POSSIBLE STEP into separate lambdas. They switched to still using microservices, but they do all transcoding steps for a single video on the same microservice instance (aka sanity).

permalink
report
parent
reply
5 points
*
Deleted by creator
permalink
report
parent
reply
2 points

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

permalink
report
parent
reply
8 points

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.

permalink
report
parent
reply
7 points

@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

permalink
report
parent
reply
5 points

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

permalink
report
reply

Programming

!programming@beehaw.org

Create post

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.

Community stats

  • 154

    Monthly active users

  • 228

    Posts

  • 1.4K

    Comments