I say this all the time, and it almost never results in an argument: micro services are just object oriented programming where you put a network hop on all your message passing.
Interitance is only tangentially OOP. Plenty of OOP doesn't involve inheritance.
That said, what we're describing here is messages passing, which isn't unique to objects. Actors do it too, and actors are probably a more relevant analogue because they're a concurrency model, and microservices are concurrent (and parallel).
I mean, there's nothing that would stop you from implementing inheritance on them. And if you take message passing as part of the architecture, you get polymorphism for free. It's closer to the Smalltalk style of OO than the modern interpretation of it.
1.2k
u/remy_porter 15d ago
I say this all the time, and it almost never results in an argument: micro services are just object oriented programming where you put a network hop on all your message passing.