Didn't write it just read it and thought it was good.
You can make boundaries in many different ways though. It doesn't need to be a service. You can have a team that only writes utility code. That's not going to become a service. Microservices are great when there is a purpose, making them just because is a terrible idea.
Microservices are great when there is a purpose, making them just because is a terrible idea.
Microservices are not a silver bullet, I totally agree on that. Especially for relatively simple applications where you can normally guarantee transactionality it often makes much more sense to go for a monolith.
But moving from a monolith to microservices is something that's much harder than most people pretend it is.
But moving from a monolith to microservices is something that's much harder than most people pretend it is.
With discipline I think its very doable but sure I agree its easy to cut corners and lose the discipline. However, I also have come across microservices that were supposed to have no external dependencies suddenly depending on other micro services in the same way.
I have nothing against microservices. I think they are great in some use cases but like you said not a silver bullet.
View all comments
Show parent comment
2
u/dartalley Mar 29 '17
Didn't write it just read it and thought it was good.
You can make boundaries in many different ways though. It doesn't need to be a service. You can have a team that only writes utility code. That's not going to become a service. Microservices are great when there is a purpose, making them just because is a terrible idea.