|
|
|
|
|
by Gluber
966 days ago
|
|
Every company i have advised jumped on the microservice bandwagon some time ago....
Here is what I tell them: 1. Microservices are a great tool... IF you have a genuine need for them
2. Decoupling in and on itself with services it not a goal
3. Developers who are bad at writing proper modular code in a monolithic setting will not magically write better code in a Microservice environment.. Rather it will get even worse since APIS ( be it GRPC, Restful or whatever ) are even harder to design
4. Most developers have NO clue about consistency or how to achieve certrain gurantees in a microservice setting ( Fun fact: My first question to developers in that area is: Define your notion of consistency, before be get to the fun stuff like RAFT or PAXOS)
5. You don't have the problems where microservices shine ( e.g banks with a few thounsands RPS )
6. Your communication overhead will dramatically increase
7. Application A that does not genuinly need microservices will be much cheaper as a monolith with proper code seperation Right now we have generation of developers and managers who don'T know any better, and just do what everybody else seems to be doing: Microservices and Scrum ... and then wonder why their costs explode. |
|