MircroServices (and a story about Netflix) | Prime React

all happy developers are alike... every unhappy developer is unhappy in their own way

So much work for something where everyone I know was like "Oh weird it starts with season 4, better switch to S1E1 manually"

The fact that this problem arised serving up Black Mirror contains irony that is not lost on me.

Watching you draw S's like a psycho feels like Black Mirror

Somewhere around 11 mins, I just started laughing as it was so clear he was completely re-enacting the video

The fact that he can just rebuild this whole system from memory shows how much he had to deal with all this every day

Wow I remember trying to introduce someone to Black Mirror after S4 but i had already watched it, and i remember how S4 would play first and it was really confusing. Can't believe that was you lmao

This skit raised my blood pressure, but the PM's reaction at the end brought it back down. Then your diagram raised it again.

4 months and multiple services for something most people considered to be a bug. I now look at my boring job in a whole different light, thanks for that. 😀

I was showing my younger brother this video and before you got around to your story. Black Mirror was mentioned and he said 'Oh, the show where they screwed up the order of the seasons.'

Lol, my friends and I just switched to S1E1 manually because it started from S4 🤣😂🤣 I feel bad for you Prime 😅

Irony is that the way he tells it, it feels like those 4 months were a black mirror episode in itself

OMG, I was like "Man, what does Black Mirror specifically have to do with microservices?". Hold onto your monoliths tight peeps. As long as you can, never let go.

People got paid like $300k a year to come up with this solution... and it took 4 months...

When you have 3600 hammers connected with unique cog sizes in a 4D map with multiple space time continuum flaws, everything starts to look like a nail to you.

Leseon learned: Dont use "smart" names for your services. Racoon, bingo, etc. It gets easier to communicate later to other devs if every service has a boring name related to what it is supposed to do.

Are you sure the service you couldn't remember why called Galactus?

I love the Netflix story here. Perfect example of microservices in practice.

I'm currently working at a place that does a hybrid microservice /monolith style of architecture. The decision to structure it this way came about from specific needs (think content creation vs content moderation) and many code refractors (services being deprecated quickly so it's hard to rely on one). The monolith single responsibility app consistently performs better than the microservices based apps. I think we'll see the industry start to realize sometimes it's better to have a tiny monolith single org responsibility style repo vs microservices hell.

Learned a lot today love Content Metadata Service uh, but we'll talk next week about adding a new reverse button player. Awesome sounds good, take care. 😂😂👌💪