Microservices are evil!

Oh, now we entered into this phase?

On JavaScript, there really is nothing else that just lets you do what you want without getting you your way. You may not be doing what you think you are doing, you may not know what you’re doing, you may be doing something ingenious, JavaScript doesn’t care it just lets you do it

Hey JS, do you want to
JS: Yes.

Great take

I have watched the entire video and I still have no clue what a monad is!

you've got a pretty good thumbnail my friend

Great video man.

I loved the JavaScript joke.

Thanks

wait for a few years then they will tell microservices are better

Perfectly said!

I use microservices since 2000. Certainly you should clear to understand what is it and how to use them with most benefits. Unfortunately it isn't obvious for everyone .

steps functions are expensive, that was the main issue with prime

"Poor choice for long running jobs and high volume jobs" ... hmm ... so that leaves just the jobs that are so simple that you could probably run them in your own basement. :)

You’re a threat homeless man! I can tell because of how effective you’ve been at attacking others…with homelessness!

Fantastic take! There's tradeoffs to EVERYTHING. "It's about using the best tool for each job". For infrequently running jobs, lambdas are great and reduce a lot of complexity to just deploy working production code. But servers still have strengths in long running, high capacity jobs. It's never black and white. If anything, I've been stuck in the serverless mindset and have been neglecting how to run my code via servers. This article was a wakeup call that I need to make sure I spend some time in each lane if I want to be a successful engineer.

Microservices only evil if you dont know how to use, setup the proper infra for it..

Please read the article carefully; there is no word that Amazon Prime Video has become a monolith. The article are talking about a separate tool created by a separate Video Quality Analysis team. they never intended nor designed it to run at high scale. That's all.

Basicallly they made a microservice that requires a new instance for each frame (as if each frame requires a new microservice) so their microservices were too chatty. If large chunks of video were processed by the same instance, this problem would not occur.

heretic!

Tbh most people don’t know how to build them. They just put monoliths in container and call it a day

Great video and explanation. I learned a new term, "denial of wallet". I always knew and feared this possibility, but didn't have a name for it.

You are damn right. Everything has tradeoffs.

When did we go from architecting to prescribing? There is no one size fits all for anything in software, each situation should be analyzed appropriately and choose the best tool for the job. In my line of work we have serverless, microservices and yes, even monoliths. What we don't do is try to force a function to do what a service does naturally and we don't horizontally scale monoliths. Nobody factors in the cost of maintenance or time to market either, it always seems to be runtime costs and performance.

Underrated channel, excellent points. I hate that the state of computing has turned into such crap where everyone needs to "modernize", essentially pushing out the nonsense buzzwords when they don't even apply to their specific problem space.