|
|
|
|
|
by gbtw
1577 days ago
|
|
In all the situations i have had to work on microservices it generally means the team just works on all the different services, now spread out over more applications. Doing more integration work vs actual business logic. Because the fancy microservices the architect wanted doesn't mean there's actually money to do it properly or even have an ops team. Also for junior team members a lot of this stuff works via magic because they can't yet oversee where the boundaries are or do not understand all the automagically configuration stuff. Also the amount of works on my machine with docker is staggering even if the developers laptop's are the same batch / imaged machine. |
|