Surely you can delivery 15 metric tons of wood with either of them. You will just need a lot of motorcycles to match capacity.
Somehow a big part of industry became convinced that of course that approach is better, since motorcycles are cheaper*, easier to scale*, and solve some managerial problems*.
* They don't, IMHO.
>its components become increasingly coupled over time
>The codebase becomes complex enough that nobody fully understands every part of it
>if a change introduces a bug - like a memory leak - the entire service can potentially be affected by it.
I believe the only real solution to those challenges is Competency, or Programmer Professionalism. Uncle Bob had some great points on this topic.
Microservices are like motorcycles.
Surely you can delivery 15 metric tons of wood with either of them. You will just need a lot of motorcycles to match capacity.
Somehow a big part of industry became convinced that of course that approach is better, since motorcycles are cheaper*, easier to scale*, and solve some managerial problems*.
* They don't, IMHO.
>its components become increasingly coupled over time
>The codebase becomes complex enough that nobody fully understands every part of it
>if a change introduces a bug - like a memory leak - the entire service can potentially be affected by it.
I believe the only real solution to those challenges is Competency, or Programmer Professionalism. Uncle Bob had some great points on this topic.
https://www.youtube.com/watch?v=BSaAMQVq01E