> This is not because microservices-first is inherently flawed. This is purely a skill set issue. Microservices demand a greater skill set. Actually, from the

> This is not because microservices-first is inherently flawed. This is purely a skill set issue. Microservices demand a greater skill set. Actually, from the perspective of someone building them for the past nine months, the actual service is the easiest part to deal with because the loose coupling drops the requirements to service constraints. The hardest part, by far, has been coordinating common changes, tracking deployments, and running no-downtime migrations. The hardest part of micro-services, BY FAR, is the management, communication, and coordination changes that MUST accompany a successful move from a monolithic codebase to many smaller codebases. Some of these are easier to address than others, but the barrier is NOT technical so much as it is social.