Seems, to me, that the author is poor at designing microservices. Using his example: the login, session and user services should be only one service (something

Seems, to me, that the author is poor at designing microservices. Using his example: the login, session and user services should be only one service (something like Keycloak), there's no advantage to splitting this up, so why would you? Analytics service should never be a dependency of another serivce, but rely on service discovery and a preset telemetry/analytics/rpc endpoint which each of the consumer-facing services implements. Has anyone claimed that microservices will fend of poor design? There's never a silver bullet.