0 views collected around this technical thread.
This article discusses why and how to split monolithic applications into microservices, outlining common pitfalls of over‑splitting and presenting practical principles such as team and domain isolation, the three‑person rule, read/write separation, dependency management, and service count guidelines.
This article explains why microservices have become a dominant architectural style, outlines the problems they solve, describes core characteristics, presents various splitting principles and methods, discusses the relationship with domain‑driven design, compares microservices to other architectures, and lists common technologies and best‑practice recommendations.
The article explains why microservices have become a mainstream architectural choice, outlines the shortcomings of monolithic systems, presents core design principles and various service‑splitting methods, discusses the synergy with Domain‑Driven Design, compares microservices with other architectures, and lists typical technologies used in practice.
This article examines the challenges of service proliferation in a microservice‑based system, defines modularity and granularity, and presents systematic splitting and merging factors—such as responsibility, fault tolerance, performance, scalability, cost‑benefit, and team size—using a concrete Promise service case study to guide optimal service design.
This article explains microservice service‑splitting principles, demonstrates a demo project with separate order and user services, and shows how to implement remote calls between them using Spring Boot's RestTemplate, including code examples and provider‑consumer concepts.
This article explains microservice service‑splitting guidelines, demonstrates a small demo project with separate order‑service and user‑service modules, shows how to define independent databases, and provides step‑by‑step code for registering a RestTemplate bean and performing remote calls between services using Spring Boot.
This article explains microservice service‑splitting principles, demonstrates a small demo with separate order‑service and user‑service modules, shows how to define independent databases, and provides step‑by‑step code for registering a RestTemplate bean and performing remote calls between services using Spring Boot.
The article explains the AKF principle for microservice design, detailing how X‑axis horizontal replication, Y‑axis functional splitting, and Z‑axis data‑centric partitioning address single‑point failures, capacity limits, and performance bottlenecks by employing master‑master, master‑slave, and master‑backup replication patterns.
The article explains how to address single‑node limitations by clustering servers using the AKF microservice splitting principle, detailing X‑axis horizontal replication, Y‑axis business‑oriented partitioning, and Z‑axis data‑source segmentation to achieve scalable, fault‑tolerant backend architectures.
This article explains why, when, and how to split a monolithic application into microservices, covering the goals of splitting, timing decisions, guiding principles, granularity considerations, functional and non‑functional strategies, merging practices, and associated risks.
The article explains the AKF microservice splitting principle, describing how X‑axis horizontal replication, Y‑axis business‑oriented partitioning, and Z‑axis data‑oriented partitioning together address single‑point failures, capacity limits, and performance bottlenecks in clustered backend systems.
This article explains why and when to split existing microservices, validates the split idea with event storming and data‑model analysis, outlines guiding principles, and provides a detailed, step‑by‑step process—including code restructuring, testing, dependency removal, and database separation—to ensure a smooth transition.
The article outlines how a call platform’s architecture progressed through successive stages—starting with a monolithic design, then business service splitting, service governance and isolated deployment, horizontal scaling, distributed database sharding, and finally micro‑service adoption—highlighting the problems each evolution solved and the new challenges introduced.
The article explains how Domain‑Driven Design (DDD) complements microservice architecture by addressing functional partitioning, clarifying bounded contexts, and guiding service decomposition, while also highlighting microservices' shortcomings in handling requirement changes and offering practical guidelines for effective system splitting.
The article explains how to build a highly scalable internet application by adopting stateless session handling, effective caching, service decomposition with remote call frameworks, database sharding, asynchronous messaging, unstructured data storage, comprehensive monitoring, and unified configuration management.