3 ms·
>Microservices, of course, exasperate this by actually increasing the communication required to make software. I'd argue the exact opposite. Microservices with
by marcinzm 6y ago
>Microservices, of course, exasperate this by actually increasing the communication required to make software.
I'd argue the exact opposite. Microservices with defined interfaces and APIs mean that everyone doesn't need to communicate with everyone. Only the people who work on a given microservice need to communicate amongst themselves. Across those groups the communication can be restricted to simply reading documented APIs. That in turn drastically lowers the amount of communication needed.
- gls2ro 6y ago> Microservices with defined interfaces and APIs mean that everyone doesn't need to communicate with everyone. This will be true if every team handling their own microservice will treat documentation like a real API like product and make it understandable, concise with clear examples. Also it needs a proper way to accept/debate bug/feature requests. But in my experience this is not happening. There is documentation but it is usually auto generated and most of the times out of date. So instead of reading it and trying to figure it out oneself it is more simpler to just contact the developer thus => more time spent in communication. The same when I need a new feature from their API I setup a meeting as usually sending an email or creating a ticket does not guarantee a response => so more communication.