85

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

all 11 comments
sorted by: hot top controversial new old
[-] xilliah@beehaw.org 12 points 9 months ago

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

Just curious what everybody thinks.

[-] ryonia@beehaw.org 11 points 9 months ago

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

[-] sarahasakura@lemmy.blahaj.zone 13 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

[-] falsem@kbin.social 3 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.

[-] ryonia@beehaw.org 2 points 9 months ago

Ahh, thanks for the info!

[-] r1veRRR@feddit.de 2 points 9 months ago

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).

[-] dark_stang@beehaw.org 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.

[-] lightninhopkins@mastodon.social 7 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

[-] Case@unilem.org 5 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
85 points (100.0% liked)

Programming

13226 readers
1 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