0 views collected around this technical thread.
Splitting a monolith into microservices can shift complexity to inter‑service communication, causing data consistency issues and CAP trade‑offs, so you must evaluate motivations, apply single‑responsibility and team‑aligned boundaries, and follow practical guidelines to ensure a sound architecture.
The article traces the rise and fall of China’s mid‑platform craze, illustrating its promise through Supercell’s profit‑driven reuse model while warning that extensive integration costs, organizational misalignment, and latency can outweigh zero‑cost benefits, and concluding that such platforms succeed only in stable domains with deep domain expertise.
The article explores how organizational structure, Conway's Law and its inverse, and the management of team cognitive load influence software architecture stability and development efficiency, offering practical measures for team design, governance, and architectural practices to align teams with desired system outcomes.
The article argues that both business and personal health debts inevitably accumulate like entropy, but can be managed through structured thinking—identifying, categorizing, prioritizing, and continuously monitoring and feedback‑driven actions such as mindfulness, exercise, and disciplined system maintenance—to reduce complexity and sustain growth.
This article summarizes the main concepts from the book “High‑Performance Team Patterns”, explaining why teams—not individuals—are the primary unit of software delivery, how Conway’s Law and the Dunbar number guide optimal team size, and presenting four basic team topologies with interaction models to enable end‑to‑end value‑stream delivery.
This article explains how team topology and Conway's Law shape communication structures, describes the concepts of flow, enabler, and complicated‑subtle teams, and offers practical guidance on aligning team cognition, applying cognitive load theory, and building value‑stream teams to improve DevOps efficiency.
The article shares a chief architect’s experience designing a hybrid “big waterfall + small agile” delivery approach, microservice architecture, BFF layer, and team organization principles such as Conway’s law to address application boundary challenges in a massive state‑owned enterprise project.
The article shares a chief architect's experience on combining a large‑scale waterfall approach with agile iterations, detailing microservice and BFF design, team organization aligned with Conway's law, and practical application‑boundary principles for a distributed enterprise system.
This article explains the challenges introduced by breaking a monolithic application into microservices, discusses CAP and BASE theories, Conway's law, and provides concrete strategies such as single‑responsibility splitting and team‑aligned architecture to help engineers design well‑structured distributed systems.
This case study details how Qunar’s hotel pricing platform was reorganized in 2021 using Domain‑Driven Design and explicit architecture principles to streamline cross‑team collaboration, reduce data‑flow complexity, and improve response time by 25%, while aligning system structure with Conway’s Law.
The article argues that merging microservices back into a monolith can be justified when service boundaries no longer align with team structures, emphasizing that microservices address both technical load and people‑organization problems, and that the right size of a service depends on context rather than the misleading notion of "micro".
The article explains how designing autonomous, end‑to‑end responsible teams—by minimizing inter‑team collaboration, adopting full‑process or cross‑functional squads, and leveraging automation tools—leads to better software architecture, aligns with Conway’s law, and improves efficiency in modern DevOps environments.
This article examines how enterprises can adopt DevOps with minimal risk and cost by leveraging agile management, continuous delivery frameworks like the 100‑to‑100 model, Conway’s Law, automation, scripting, and containerization with Docker, while also presenting a recruitment call for DevOps engineers.
The article explains how Conway's Law—stating that system designs mirror organizational communication structures—provides a theoretical foundation for microservices, highlighting communication costs, team size limits, resilience, and practical guidelines for building autonomous, business‑oriented service teams.
This article explains how applying first‑principles thinking to product development helps avoid "goods worship" and guides the design of scalable lean‑agile processes that focus on smooth, high‑quality delivery of valuable outcomes, illustrated with real‑world examples and practical frameworks.
At SpringOne, Credera engineers Jason Goth, Micah Blalock, and Patricia Anderson explained how they leveraged Conway’s Law to redesign a client’s technical architecture and processes, overcoming productivity decline by restructuring teams, applying the open/closed principle, and introducing new communication roles, ultimately accelerating high‑quality code delivery.