MircroServices (and a story about Netflix) | Prime React

Primeagen has a good overview of how microservices worked at Netflix. It's in the latter half of the video but the full video is still entertaining.

Miserable life caused by microservices at scale?

I used to be the problem - and I can tell you what I think it is: 1. Assuming it's hard or extraordinarily time-consuming to write (and learn to write) code that isn't orders of magnitude slower than the CPU can do, even without taking advantages of its advanced optimizations. I certainly assumed so, but I just never saw a real example of how to do it right. And do you know what I've found? Web development, which is generally touted as the easiest, is actually far harder than doing code that also touches low-level parts. Because web development is so unpredictable, opaque, imprecise and hard to debug. Low-level code, on the other hand, just does exactly what you tell it to do. You're only r…

He definitely has problems with polymorphism. Because it involves V-tables which are inherently opaque (because the compiler can implement it in different ways) and virtually always cause cache misses. And because (as far as I understand it) he has experience with that being one of the main reasons that his code was slow back when he used to blindly trust C++ developers knew what they were doing. He's not even saying you should optimize your code. He's saying that if you just take a short while to understand the hardware, and how to evaluate code (rather than just trusting), then you'll be writing code that is faster by orders of magnitude. No hardware optimization is needed. And in his…

Maybe you're right that it's an ambiguous thing. When I studied Computer Science 10 years ago, it meant creating classes with functions, like "Apple : Fruit" and "Enumerator<Fruit>" - and the more advanced version is SOLID where you not only make use of common "design patterns", but also make heavy use of interfaces and ideas like dependency injection, to fix some of the rigidity problems of OOP. Beside the massive performance cost of those ideas, it's also extremely complex to get right, in my experience. Very few places I've seen are good at following SOLID, and it's not uncommon that when you're deep into the weeds of this mentality, simply displaying simple data ([like reordering episode…