BestHub
Sign in
Tagged articles
66 articles
Page 1 of 1
IT Services Circle
IT Services Circle
May 15, 2026 · Backend Development

When Splitting a System into 200 Microservices Almost Ruined the Company

The article uses a night‑market analogy to explain practical microservice design, covering domain‑based service decomposition, service discovery, communication protocols, data consistency strategies, fault‑tolerance, rate limiting, and monitoring, while warning against over‑splitting and unnecessary complexity.

Distributed TracingMicroservicescircuit breaker
0 likes · 14 min read
When Splitting a System into 200 Microservices Almost Ruined the Company
Java Tech Enthusiast
Java Tech Enthusiast
May 15, 2026 · Backend Development

How Splitting a System into 200 Microservices Almost Destroyed Our Company

The article uses a night‑market analogy to explain common microservice pitfalls—over‑splitting, poor service boundaries, fragile communication, data‑consistency challenges, fault‑tolerance, rate‑limiting, and monitoring—providing concrete examples, best‑practice rules, and Java code snippets to help teams avoid costly mistakes.

Distributed TracingMicroservicescircuit breaker
0 likes · 15 min read
How Splitting a System into 200 Microservices Almost Destroyed Our Company
Top Architect
Top Architect
Apr 10, 2026 · Backend Development

Essential Microservice Design Patterns Every Architect Should Know

This article provides a comprehensive overview of microservice architecture, outlining its core goals, design principles, and a wide range of decomposition, integration, database, event‑driven, observability, and cross‑cutting concern patterns, complete with practical examples and diagrams.

Backend ArchitectureDesign PatternsMicroservices
0 likes · 22 min read
Essential Microservice Design Patterns Every Architect Should Know
Architect's Guide
Architect's Guide
Feb 21, 2026 · Backend Development

Essential Microservice Design Patterns Every Backend Engineer Should Know

This article surveys common microservice design patterns—including decomposition, integration, event‑driven, cross‑cutting concerns, and observability—explaining their goals, trade‑offs, and practical implementation steps to help architects build scalable, resilient backend systems.

Backend ArchitectureMicroservicesObservability
0 likes · 20 min read
Essential Microservice Design Patterns Every Backend Engineer Should Know
Architect's Journey
Architect's Journey
Dec 5, 2025 · Backend Development

Capacity‑Driven Microservice Architecture: Solving High‑Concurrency Challenges

The article explains how a capacity‑driven microservice architecture uses performance metrics like QPS, TPS, and latency as the primary split criterion, detailing design principles, module responsibilities, and practical benefits that enable systems to handle traffic spikes without service collapse.

Domain-Driven DesignMicroservicescapacity‑driven architecture
0 likes · 10 min read
Capacity‑Driven Microservice Architecture: Solving High‑Concurrency Challenges
Code Ape Tech Column
Code Ape Tech Column
Jun 17, 2025 · Backend Development

When Splitting Microservices Backfires: Risks and Smart Strategies

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.

Backend ArchitectureCAP theoremConway's law
0 likes · 11 min read
When Splitting Microservices Backfires: Risks and Smart Strategies
Architect
Architect
Jan 7, 2025 · Backend Development

When Should You Split or Merge Microservices? A Practical Guide

This article examines the principles of microservice decomposition and composition, analyzes the risks of improper service splitting such as communication overhead, dependency loops, and chaotic call chains, and offers concrete governance strategies to achieve a balanced, maintainable architecture.

BackendMicroservicesSystem Design
0 likes · 10 min read
When Should You Split or Merge Microservices? A Practical Guide
Top Architect
Top Architect
Aug 6, 2024 · Backend Development

Why and How to Adopt Microservices: Principles, Design Strategies, and Comparison with Other Architectures

The article explains why microservices have become a mainstream architectural style, outlines the problems of monolithic systems, presents core microservice characteristics, offers practical decomposition principles and patterns, compares microservices with monolith, distributed, serverless, SOA and service‑mesh architectures, and lists common technology stacks for implementation.

Backend ArchitectureDomain-Driven Designcloud-native
0 likes · 26 min read
Why and How to Adopt Microservices: Principles, Design Strategies, and Comparison with Other Architectures
Mike Chen's Internet Architecture
Mike Chen's Internet Architecture
May 31, 2024 · Backend Development

Mastering Microservice Splitting: 6 Essential Design Principles

This article outlines six fundamental microservice splitting principles—including single responsibility, appropriate granularity, interface segregation, product impact avoidance, scalability, and fault tolerance—to help architects design maintainable, decoupled, and resilient services.

MicroservicesScalabilityfault tolerance
0 likes · 5 min read
Mastering Microservice Splitting: 6 Essential Design Principles
Architect's Guide
Architect's Guide
May 24, 2024 · Backend Development

Designing an API Layer and BFF Architecture for a Large‑Scale Supply Chain System

This article explains how a complex supply‑chain platform with dozens of services and two client apps can be reorganized by introducing a gateway, an API aggregation layer, and a Backend‑for‑Frontend (BFF) pattern to reduce service coupling, simplify interface placement, and improve client‑specific adaptations.

BFFMicroservicesSpring Cloud
0 likes · 11 min read
Designing an API Layer and BFF Architecture for a Large‑Scale Supply Chain System
dbaplus Community
dbaplus Community
May 8, 2024 · Backend Development

10 Common Pitfalls When Adopting Spring Cloud Alibaba Microservices (And How to Avoid Them)

The article shares ten real‑world problems encountered in a Spring Cloud Alibaba microservice project—ranging from poor service decomposition and shared databases to chaotic configuration, unnecessary components, and deployment mistakes—offering insights to help teams prevent similar pitfalls.

Backend ArchitectureConfiguration ManagementMicroservices
0 likes · 7 min read
10 Common Pitfalls When Adopting Spring Cloud Alibaba Microservices (And How to Avoid Them)
Architect
Architect
Oct 15, 2023 · Backend Development

Reflections on Microservices: Promises, Realities, and Trade‑offs

The article examines the alluring promises of microservices—such as faster deployments, independent scaling, and team autonomy—while revealing the hidden complexities like deployment chaos, service discovery, data consistency, latency, and the nostalgic appeal of monolithic architectures, ultimately offering three key takeaways for architects.

Backend ArchitectureDistributed SystemsMicroservices
0 likes · 10 min read
Reflections on Microservices: Promises, Realities, and Trade‑offs
Programmer DD
Programmer DD
Sep 13, 2023 · Backend Development

When Microservice Refactoring Turns Into a Distributed Monolith: Risks and Remedies

The article examines why many microservice migrations end up as distributed monoliths, highlighting the hidden costs, stability issues, and common pitfalls such as excessive synchronous calls and lack of protection mechanisms, and offers practical guidance to avoid these traps.

Backend Architecturedistributed monolithservice decomposition
0 likes · 7 min read
When Microservice Refactoring Turns Into a Distributed Monolith: Risks and Remedies
Programmer DD
Programmer DD
Mar 20, 2023 · Backend Development

Is Your ‘Distributed Monolith’ Undermining Microservice Benefits?

The article examines the pitfalls of turning a monolithic application into a ‘distributed monolith’ during microservice migration, highlighting how improper domain splitting, excessive synchronous remote calls, and lack of protective mechanisms can degrade stability and negate expected productivity gains.

Backend ArchitectureMicroservicesdistributed monolith
0 likes · 7 min read
Is Your ‘Distributed Monolith’ Undermining Microservice Benefits?
Architecture Digest
Architecture Digest
Feb 23, 2023 · Backend Development

Decomposing Monolithic Applications into Microservices: Business Capability, Subdomain, and Strangler Patterns

The article explains how to break down large or legacy monolithic systems into microservices by using business‑capability and sub‑domain decomposition approaches, discusses the benefits and challenges of such refactoring, and introduces the Strangler pattern for gradual migration.

Subdomainbusiness capabilitymonolith
0 likes · 6 min read
Decomposing Monolithic Applications into Microservices: Business Capability, Subdomain, and Strangler Patterns
Code Ape Tech Column
Code Ape Tech Column
Jan 29, 2023 · Backend Development

Microservice Splitting Strategies: Expert Perspectives and Practical Guidelines

The article discusses various expert approaches to microservice decomposition, highlighting vertical and horizontal splits, business logic, stability, reliability, performance considerations, and team size implications, offering practical guidance for backend architects in design.

Backend ArchitectureTeam Organizationservice decomposition
0 likes · 10 min read
Microservice Splitting Strategies: Expert Perspectives and Practical Guidelines
Architecture Digest
Architecture Digest
Dec 9, 2022 · Backend Development

Using Domain-Driven Design to Split Microservices

This article explains how Domain-Driven Design (DDD) can guide the decomposition of monolithic applications into microservices by introducing strategic and tactical design concepts, illustrating them with a membership‑center example, and providing detailed Go code structures and implementations.

DDDGoservice decomposition
0 likes · 14 min read
Using Domain-Driven Design to Split Microservices
IT Architects Alliance
IT Architects Alliance
Dec 6, 2022 · Backend Development

A Comprehensive Guide to Service Splitting in Microservice Architecture

This article systematically explores the challenges of microservice service splitting—from technical choices and architectural reliability to business model validation and team collaboration—offering static and dynamic solutions, design principles, and practical guidelines for effective service decomposition.

Software ArchitectureSystem Designbackend design
0 likes · 7 min read
A Comprehensive Guide to Service Splitting in Microservice Architecture
Alibaba Cloud Native
Alibaba Cloud Native
Dec 6, 2022 · Cloud Native

Mastering Full‑Chain Gray Deployments in Cloud‑Native Microservices

This article explains the fundamentals of full‑chain gray releases in microservice architectures, covering service hierarchy, high‑cohesion low‑coupling design, deployment strategies with Kubernetes namespaces, traffic routing rules, and the essential infrastructure components needed for robust cloud‑native applications.

Microservicesgray releaseservice decomposition
0 likes · 9 min read
Mastering Full‑Chain Gray Deployments in Cloud‑Native Microservices
Code Ape Tech Column
Code Ape Tech Column
Oct 9, 2022 · Backend Development

Reasonable Microservice Splitting: Problems, Principles, and Practical Guidelines

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.

Backend ArchitectureCAP theoremConway's law
0 likes · 11 min read
Reasonable Microservice Splitting: Problems, Principles, and Practical Guidelines
Programmer DD
Programmer DD
Aug 3, 2022 · Backend Development

Why Your “Distributed Monolith” Is Still a Single Point of Failure

The article explains how many microservice migrations end up as “distributed monoliths,” detailing why splitting a monolith without proper domain design and protective mechanisms can worsen stability, increase latency, and fail to deliver the promised efficiency gains.

MicroservicesSoftware Architecturedistributed monolith
0 likes · 7 min read
Why Your “Distributed Monolith” Is Still a Single Point of Failure
Baidu Geek Talk
Baidu Geek Talk
Jul 25, 2022 · Backend Development

Baidu Wenku Download Service Microservices Transformation Practice

Baidu Wenku revamped its download function by breaking the monolith into an independent microservice, establishing unified protocols, a modular framework for security, rate‑limiting and logging, and real‑time monitoring, which reduced maintenance costs, improved user experience, and enabled rapid, system‑wide updates.

Baidu WenkuMicroservicesSystem Design
0 likes · 16 min read
Baidu Wenku Download Service Microservices Transformation Practice
Architect
Architect
Jun 6, 2022 · Backend Development

Microservice Architecture and Design Patterns

This article provides a comprehensive overview of microservice architecture, detailing its core objectives, design principles, various decomposition and integration patterns, database strategies, consistency mechanisms, observability techniques, and deployment practices for building resilient, scalable backend systems.

MicroservicesObservabilityarchitecture
0 likes · 18 min read
Microservice Architecture and Design Patterns
Architect's Journey
Architect's Journey
Mar 9, 2022 · Backend Development

What Factors Should You Consider When Splitting Microservices?

The article explains how breaking a monolith into microservices can introduce data consistency challenges, discusses the CAP theorem and Conway's law, and provides practical guidelines—such as single‑responsibility division, team‑aligned service boundaries, and appropriate use of BASE and distributed transactions—to split services responsibly.

CAP theoremConway's lawTeam Organization
0 likes · 11 min read
What Factors Should You Consider When Splitting Microservices?
Architecture & Thinking
Architecture & Thinking
Jan 7, 2022 · Backend Development

How to Prepare and Execute a Successful Microservice Migration

This article outlines the essential preparations, strategic service granularity decisions, and practical splitting techniques—based on business logic, scalability, reliability, and performance—to guide teams in migrating monolithic systems to a robust microservice architecture.

Backend Architecturemigrationservice decomposition
0 likes · 10 min read
How to Prepare and Execute a Successful Microservice Migration
Java Architect Essentials
Java Architect Essentials
Aug 19, 2021 · Backend Development

When and How to Adopt Microservices: Evaluation, Risks, and Best Practices

This article examines the transition from monolithic to microservice architectures, outlining the advantages and costs of microservices, the conditions under which they should be adopted, practical implementation options, risk assessments, service‑splitting strategies, and a concise comparison with SOA.

architecturerisk assessmentservice decomposition
0 likes · 17 min read
When and How to Adopt Microservices: Evaluation, Risks, and Best Practices
IT Architects Alliance
IT Architects Alliance
Aug 8, 2021 · Backend Development

Introduction to Microservices Architecture: Concepts, Benefits, Challenges, and Implementation Strategies

This article explains the fundamentals of microservices architecture, compares it with monolithic (integrated) systems, outlines the problems solved by microservices, details their advantages and disadvantages, provides a practical Java Spring example with code snippets, and discusses strategies for service decomposition and migration.

BackendDevOpsMicroservices
0 likes · 20 min read
Introduction to Microservices Architecture: Concepts, Benefits, Challenges, and Implementation Strategies
ITFLY8 Architecture Home
ITFLY8 Architecture Home
Aug 7, 2021 · Backend Development

Why Microservices Matter: From Monoliths to Scalable Architecture

This article explains the fundamentals of microservice architecture, contrasts it with monolithic designs, outlines the problems microservices solve, lists their advantages and drawbacks, provides a hands‑on code example, and describes practical strategies for splitting and migrating legacy systems.

BackendMicroservicesarchitecture
0 likes · 19 min read
Why Microservices Matter: From Monoliths to Scalable Architecture
IT Architects Alliance
IT Architects Alliance
Aug 3, 2021 · Industry Insights

How to Split Complex Systems and Evolve Architecture for Scalable Micro‑services

The article examines why growing business complexity and throughput demands necessitate system decomposition and architectural evolution, detailing horizontal scaling, vertical and business splitting, database partitioning strategies, cache and index integration, remote service data sourcing, and asynchronous messaging to achieve scalable, robust micro‑service‑based solutions.

MicroservicesSystem Architectureasynchronous messaging
0 likes · 9 min read
How to Split Complex Systems and Evolve Architecture for Scalable Micro‑services
Top Architect
Top Architect
Jun 29, 2021 · Backend Development

Microservices Architecture: Principles, Benefits, Drawbacks, and Practical Implementation Guide

This comprehensive article explains the microservices architectural style, contrasts it with monolithic (integrated) architecture, outlines the problems solved by microservices, details design principles, splitting strategies, patterns such as Strangler and Rehab, and provides a complete Java SpringBoot example with code snippets and deployment instructions.

DevOpsDistributed Systemsservice decomposition
0 likes · 23 min read
Microservices Architecture: Principles, Benefits, Drawbacks, and Practical Implementation Guide
Architects' Tech Alliance
Architects' Tech Alliance
Jun 28, 2021 · Backend Development

Understanding the Essence of Architecture and Weibo's Large‑Scale System Design

This article explores the fundamental concepts of software architecture, illustrates scaling challenges with examples like Uber and Weibo, and details multi‑tier designs, caching strategies, service decomposition, monitoring, and operational practices for building and maintaining high‑performance, billion‑user backend systems.

BackendScalabilitycaching
0 likes · 20 min read
Understanding the Essence of Architecture and Weibo's Large‑Scale System Design
Architect
Architect
Jun 27, 2021 · Backend Development

Understanding Microservices Architecture: Principles, Benefits, Challenges, and Implementation Strategies

This article explains microservices architecture, contrasting it with monolithic systems, outlines the problems it solves, lists its advantages and disadvantages, provides a concrete service example with code, and discusses strategies, principles, and patterns for splitting and evolving microservices.

Backend ArchitectureDevOpsservice decomposition
0 likes · 18 min read
Understanding Microservices Architecture: Principles, Benefits, Challenges, and Implementation Strategies
Programmer DD
Programmer DD
May 16, 2021 · Backend Development

What Really Drives Scalable Backend Architecture? Lessons from Weibo’s Massive System

This article explores the essence of system architecture, illustrating how large‑scale services like Uber and Weibo handle massive traffic, data storage, service decomposition, multi‑level caching, and monitoring, and offers practical design principles for building robust, high‑performance backend systems.

Backend ArchitecturePerformance OptimizationScalable Systems
0 likes · 22 min read
What Really Drives Scalable Backend Architecture? Lessons from Weibo’s Massive System
IT Architects Alliance
IT Architects Alliance
Mar 22, 2021 · Backend Development

Why Microservices Need DDD: Solving Complexity in Modern Systems

The article examines the limitations of microservice architectures, explains how Domain‑Driven Design (DDD) complements them by providing functional decomposition guidance, and presents a practical case study showing how clear bounded contexts and aggregate roots enable scalable, maintainable system splits.

DDDDomain-Driven DesignMicroservices
0 likes · 9 min read
Why Microservices Need DDD: Solving Complexity in Modern Systems
Top Architect
Top Architect
Jan 20, 2021 · Backend Development

Key Practices and Considerations in Microservice Architecture Design

The article explores practical design principles for microservice architecture, covering core concepts, team and database partitioning, API granularity, domain‑composed services, gateway strategies, shared JAR dependencies, decoupling techniques, and change‑impact analysis to guide robust backend system development.

Backend ArchitectureMicroservicesapi-design
0 likes · 16 min read
Key Practices and Considerations in Microservice Architecture Design
IT Architects Alliance
IT Architects Alliance
Nov 4, 2020 · Industry Insights

When Should You Switch to Microservices? A Practical Evaluation Guide

This article examines the trade‑offs between monolithic and microservice architectures, outlines the benefits, costs, and technical prerequisites of microservices, and provides concrete criteria—such as business complexity, team size, and talent readiness—to help engineers decide the right moment to adopt a microservice approach.

DeploymentMicroservicesTechnical Debt
0 likes · 17 min read
When Should You Switch to Microservices? A Practical Evaluation Guide
ITFLY8 Architecture Home
ITFLY8 Architecture Home
Oct 2, 2020 · Backend Development

How to Split Microservices: 3 Expert Strategies for Effective Service Decomposition

This article compares three seasoned experts' approaches to microservice splitting—vertical vs. horizontal, business‑driven, stability‑driven, and performance‑driven—highlighting trade‑offs, team size considerations, and practical guidelines for achieving scalable, maintainable architectures.

Backend ArchitectureMicroservicesTeam Organization
0 likes · 9 min read
How to Split Microservices: 3 Expert Strategies for Effective Service Decomposition
Top Architect
Top Architect
Sep 6, 2020 · Cloud Native

Microservice Architecture: Evaluation, Adoption Timing, and Implementation Considerations

This article examines the transition from monolithic to microservice architecture, outlining the benefits and drawbacks of each, the conditions under which microservices should be adopted, the necessary technical and team resources, risk assessments, and practical guidance on service decomposition and migration.

Microservicesarchitecturerisk assessment
0 likes · 18 min read
Microservice Architecture: Evaluation, Adoption Timing, and Implementation Considerations
Top Architect
Top Architect
Aug 21, 2020 · Backend Development

Various Approaches to Service Decomposition in Microservice Architecture

The article explores multiple expert perspectives on how to split monolithic applications into microservices, discussing vertical and horizontal decomposition, business logic, stability, reliability, performance, team size, and practical trade‑offs to guide architects in designing scalable, maintainable systems.

BackendMicroserviceScalability
0 likes · 9 min read
Various Approaches to Service Decomposition in Microservice Architecture
Architect
Architect
Aug 17, 2020 · Backend Development

Various Approaches to Microservice Decomposition

The article examines microservice architecture as an abstract concept and presents three practical decomposition strategies—vertical/horizontal business split, business‑driven and team‑oriented considerations, and criteria based on logic, stability, reliability and performance—while also discussing cost, release frequency, and team size implications.

Backend ArchitectureTeam Organizationservice decomposition
0 likes · 8 min read
Various Approaches to Microservice Decomposition
Architect
Architect
Aug 1, 2020 · Backend Development

Core Concepts of Microservice Architecture and Its Relationship with Domain‑Driven Design

This article explains the fundamental differences between microservice architecture and traditional SOA, emphasizes the importance of proper service boundaries and DDD‑guided decomposition, and compares transaction‑script (anemic) and rich‑model approaches with code examples to illustrate how domain‑centric design improves microservice implementations.

Backend Architectureservice decomposition
0 likes · 12 min read
Core Concepts of Microservice Architecture and Its Relationship with Domain‑Driven Design
Architects Research Society
Architects Research Society
Apr 6, 2020 · Backend Development

Evaluating Microservice Architecture for Large Enterprises: Benefits, Challenges, and Governance

This article examines whether microservice architecture suits large organizations by outlining its cultural, technical, and operational impacts, the reasons to decompose monolithic systems, key considerations for architects, and practical guidance on avoiding deployment coupling while managing complexity.

Backend ArchitectureMicroservicesdeployment coupling
0 likes · 9 min read
Evaluating Microservice Architecture for Large Enterprises: Benefits, Challenges, and Governance
Cloud Native Technology Community
Cloud Native Technology Community
Mar 18, 2020 · Backend Development

Microservice Splitting Strategies: Perspectives and Practices

The article explores various microservice decomposition approaches—vertical vs. horizontal, business‑driven, stability‑based, reliability‑focused, and performance‑oriented—highlighting trade‑offs, team size considerations, and practical guidelines for achieving scalable, maintainable service architectures.

MicroservicesSoftware ArchitectureTeam Organization
0 likes · 9 min read
Microservice Splitting Strategies: Perspectives and Practices
Architecture Digest
Architecture Digest
Mar 4, 2020 · Backend Development

Microservice Splitting Strategies: Three Approaches and Practical Considerations

This article examines microservice decomposition by presenting three expert‑derived splitting approaches—vertical/horizontal, business‑driven cost‑aware, and responsibility‑based—and discusses how factors such as team size, maintenance cost, scalability, stability, reliability and performance influence the optimal service boundaries.

Backend ArchitectureMicroservicesScalability
0 likes · 8 min read
Microservice Splitting Strategies: Three Approaches and Practical Considerations
Architecture Digest
Architecture Digest
Jul 24, 2019 · Backend Development

Legacy System Migration Strategies for Microservice Architecture

This article examines the challenges of legacy systems and presents evolutionary migration, strangler, and sidecar patterns—along with data‑sync solutions and a real‑world case study—to guide incremental, low‑cost transformation of monolithic applications into microservices while preserving business continuity.

legacy systemmigrationservice decomposition
0 likes · 27 min read
Legacy System Migration Strategies for Microservice Architecture
Java High-Performance Architecture
Java High-Performance Architecture
Apr 23, 2019 · Backend Development

How to Effectively Split a Large System into Microservices?

This article explains how to determine the appropriate number of microservices for a large system and outlines four practical splitting strategies—by business logic, scalability, reliability, and performance—while emphasizing team size and service granularity to balance maintainability and efficiency.

Backend ArchitectureMicroservicesSystem Design
0 likes · 6 min read
How to Effectively Split a Large System into Microservices?
ITFLY8 Architecture Home
ITFLY8 Architecture Home
Jul 22, 2018 · Backend Development

How Evolutionary Architecture Transforms Monoliths into Agile Microservices

This article examines evolutionary architecture for microservices, outlines popular patterns such as CI/CD and the Strangler approach, explains layered and bounded‑context designs, and provides a detailed case study showing how a legacy monolithic system can be incrementally refactored into a flexible, cloud‑native microservice ecosystem.

Microservicesci/cdcloud
0 likes · 45 min read
How Evolutionary Architecture Transforms Monoliths into Agile Microservices
Architecture Digest
Architecture Digest
Jul 7, 2018 · Backend Development

Lessons and Reflections on Service‑Oriented Architecture and Microservice Evolution at Zhihu

The article shares Zhihu's multi‑year journey toward service‑oriented architecture, discussing the motivations, practical challenges, design trade‑offs, and lessons learned from microservice, RPC, and SSO‑based vertical splitting, as well as guidelines for defining service boundaries and layering.

Backend ArchitectureRPCSSO
0 likes · 10 min read
Lessons and Reflections on Service‑Oriented Architecture and Microservice Evolution at Zhihu
21CTO
21CTO
May 23, 2018 · Backend Development

How to Evolve a Monolithic System into a Distributed, Service‑Oriented Architecture

This article explains why growing business complexity and throughput demands force a system to be split and refactored, describing horizontal scaling, vertical and business splitting, database sharding, and the resulting architectural evolution toward micro‑services.

MicroservicesSystem Architecturedatabase sharding
0 likes · 9 min read
How to Evolve a Monolithic System into a Distributed, Service‑Oriented Architecture
ITFLY8 Architecture Home
ITFLY8 Architecture Home
May 12, 2018 · Backend Development

What Drives the Architecture of Billion‑User Platforms? Lessons from Weibo

This article explores the essence of system architecture for massive web services, illustrating strategic and tactical considerations through examples like Uber and Weibo, and discusses key capabilities such as abstraction, classification, performance, service decomposition, multi‑level caching, distributed tracing, and continuous learning for scalable backend design.

Distributed SystemsPerformance OptimizationSystem Architecture
0 likes · 21 min read
What Drives the Architecture of Billion‑User Platforms? Lessons from Weibo
ITFLY8 Architecture Home
ITFLY8 Architecture Home
May 1, 2018 · Backend Development

How Yirendai Scaled Its Internet Finance Platform: From 1.0 to 4.0

This article examines how Yirendai tackled the high‑concurrency, big‑data challenges of internet finance by evolving its architecture through four major versions, introducing performance optimizations, service decomposition, database scaling, and cloud‑native strategies to support massive user growth while preserving a seamless customer experience.

BackendPerformance OptimizationSystem Architecture
0 likes · 14 min read
How Yirendai Scaled Its Internet Finance Platform: From 1.0 to 4.0
dbaplus Community
dbaplus Community
Mar 29, 2018 · Backend Development

When to Split a Monolith into Microservices: Practical Guidelines and a Step‑by‑Step Example

The article examines the advantages and drawbacks of microservices versus monolithic architectures, outlines key factors that influence the decision to split, and walks through a real‑world shared‑points project, detailing a four‑step process for decomposing a monolith into independent services.

Backend ArchitectureGoProtobuf
0 likes · 10 min read
When to Split a Monolith into Microservices: Practical Guidelines and a Step‑by‑Step Example
ITFLY8 Architecture Home
ITFLY8 Architecture Home
Jan 18, 2018 · Backend Development

Why Microservices? Designing Scalable Backend Architecture with Scale Cube

Microservice architecture, built using the Scale Cube Y‑axis approach, splits backend functionality into independent services with dedicated databases, enabling rapid development, continuous deployment, scalability, and fault isolation, while also introducing complexities such as distributed system management, testing challenges, and higher resource consumption.

Continuous DeploymentMicroservicesscale cube
0 likes · 11 min read
Why Microservices? Designing Scalable Backend Architecture with Scale Cube
Qunar Tech Salon
Qunar Tech Salon
Jul 24, 2017 · Backend Development

Addressing Service Decomposition Challenges with Event‑Driven Architecture in Transaction Systems

The article explains how a transaction system evolved from a monolithic application to a service‑oriented design, tackling issues such as RPC‑induced coupling, state explosion, and distributed consistency by introducing reliable event‑driven mechanisms, a core StoreEngine, and an ActorEngine framework.

Event-drivenReliabilityactor-model
0 likes · 8 min read
Addressing Service Decomposition Challenges with Event‑Driven Architecture in Transaction Systems
DevOps
DevOps
Mar 30, 2017 · Cloud Native

Understanding Microservice Architecture: A Comparison with Monolithic Systems

The article explains microservice architecture as a set of small, independently deployable services communicating via lightweight protocols, contrasts it with monolithic applications, and discusses its benefits, challenges, organizational impact, and common integration patterns such as REST, messaging buses, and service boundaries.

architecturemonolithicrest
0 likes · 11 min read
Understanding Microservice Architecture: A Comparison with Monolithic Systems
Ctrip Technology
Ctrip Technology
Nov 22, 2016 · Backend Development

Evolution and Service Decomposition of Qunar's Payment System (1.0 → 2.0)

The article outlines the five‑year evolution of Qunar's payment platform from a tightly coupled monolith (1.0) to a highly available, service‑oriented distributed architecture (2.0), detailing component breakdown, challenges, and the resulting core transaction, payment, cashier, and API layers.

Backend ArchitectureDistributed Systemsfinancial technology
0 likes · 9 min read
Evolution and Service Decomposition of Qunar's Payment System (1.0 → 2.0)
Qunar Tech Salon
Qunar Tech Salon
Nov 11, 2016 · Backend Development

Evolution and Service Decomposition of Qunar's Payment System

This article chronicles the five‑year evolution of Qunar's payment platform from a tightly coupled monolithic system to a high‑concurrency, highly available distributed architecture, detailing the motivations, service‑oriented splits, core components, and checkout variations that enabled support for diverse payment scenarios.

Backend ArchitectureQunarpayment system
0 likes · 9 min read
Evolution and Service Decomposition of Qunar's Payment System
Qunar Tech Salon
Qunar Tech Salon
Aug 23, 2016 · Backend Development

Evolution of Qunar Flight Ticket Transaction System Architecture and Database Refactoring

This article details the step‑by‑step evolution of Qunar's domestic flight ticket transaction system, covering early monolithic design, service‑oriented decomposition, database schema migration, adoption of non‑relational storage, and the implementation of an ELK‑based logging and monitoring platform to improve scalability and maintainability.

ELKOrder ManagementSystem Architecture
0 likes · 22 min read
Evolution of Qunar Flight Ticket Transaction System Architecture and Database Refactoring