Re:So many bad takes. Learn from the Prime Video microservic...
by bcrosby95 on Sunday May 07, 2023 @02:24PM
(#35854118)
How about spaghetti architecture.
Re:So many bad takes. Learn from the Prime Video microservic...
by jpgvm on Sunday May 07, 2023 @02:31PM
(#35854173)
I like that one.
Re:So many bad takes. Learn from the Prime Video microservic...
by hyperhopper on Sunday May 07, 2023 @02:55PM
(#35854429)
Re:So many bad takes. Learn from the Prime Video microservic...
by jpgvm on Sunday May 07, 2023 @02:09PM
(#35853982)
Yeah I completely agree with all of that.
Re:So many bad takes. Learn from the Prime Video microservic...
by goalieca on Sunday May 07, 2023 @02:56PM
(#35854442)
> Spaghetti code is more of a term for monolithic mess where you have a hard time following all the code logic (cyclomatic complexity) and dependencies.
I started using distributed monolith.
Re:So many bad takes. Learn from the Prime Video microservic...
by ohmahjong on Sunday May 07, 2023 @03:24PM
(#35854722)
I saw this described recently as the "Lambda Pinball" architecture.
* https://www.thoughtworks.com/radar/techniques?blipid=2019110...
Re:So many bad takes. Learn from the Prime Video microservic...
by jpgvm on Sunday May 07, 2023 @04:21PM
(#35855264)
When even Thoughtworks thinks you are doing it wrong you know you are in trouble.
Re:So many bad takes. Learn from the Prime Video microservic...
by bawolff on Sunday May 07, 2023 @06:16PM
(#35856142)
> Spaghetti code is more of a term for monolithic mess where you have a hard time following all the code logic (cyclomatic complexity) and dependencies.
The only thing worse than a monolithic mess, is the same thing but distributed
> Turns all your code into spagetti, this is probably the biggest one.
Overall agree with you, but I don't think spaghetti is the right term here - even if the typo is corrected :)
Spaghetti code is more of a term for monolithic mess where you have a hard time following all the code logic (cyclomatic complexity) and dependencies.
Understanding & tracking dependencies is actually easier with serveless, it's pretty clear what dependency that one tiny micro service has.
But where it becomes worse is regarding the code logic mess, you've now turned it in a distributed system problem where, in addition to having a even hard time with cyclomatic complexity, you also have to think about transient failures/retries at each service boundaries.
That and the other problems you describe (performance hit etc)