3 ms·
Microservices was a terrible buzzword and definitely made me re-evaluate the kool-aids I had previously drank from Martin Fowler. We already had services and s
by jokethrowaway 5y ago
Microservices was a terrible buzzword and definitely made me re-evaluate the kool-aids I had previously drank from Martin Fowler.
We already had services and service oriented architecture. Finding the correct size and establishing boundaries between services is a huge part of a correct architecture.
Building a monolith was a first step, then companies were branching out different parts in other services, when and if needed (eg. when doing acquisitions, as you mentioned).
Microservices just pushed companies to write services that were too small (I still remembers thought leaders praising 20 lines microservices) and declare dinosaurs everyone doing monoliths.
Your ‘successfully moved the app from .net 2 to .net 4’ becomes `updated all versions of the logger in all microservices`.
- jameshart 5y agoKey difference for me between microservice architecture and service oriented architecture is the move away from a shared database. Switching to small, single purpose datastores is the much bigger shift in thinking than small, single purpose components.