The article dives into the chaos of microservices, highlighting ongoing challenges that persist despite advancements in technology. The author, João Q. Alves, shares insights from his experience at Adevinta, particularly focusing on four new disasters in a microservices environment. The first issue is the imbalance of services and engineers. Many teams end up with four to five services per engineer, leading to overload. While major tech companies can manage this due to robust platforms, most organizations struggle, resulting in cognitive overhead and orphaned services that no one wants to shut down. Another critical point is the complexity of the gateway layer, which connects frontends and microservices. Teams often underestimate the demands of authentication and authorization, leading to gateways that falter under heavy loads. Misconfigured thread pools can cause latency spikes and system failures. The third disaster revolves around technology sprawl, where engineers adopt a myriad of frameworks and libraries without oversight. This approach can create operational headaches, especially when key team members leave, taking their unique knowledge with them. Lastly, the author addresses the problem of aligning organizational structure with architectural design. Teams often create microservices based on ownership rather than functional domains, leading to tangled dependencies when team structures change. This misalignment can result in costly technical debt that becomes apparent only when reorganization occurs. The article emphasizes that while tools and frameworks evolve, the fundamental issues of complexity and human behavior in distributed systems remain unchanged.