Tagged articles
monolith
69 articles · Page 1 of 1
This chapter summary traces the evolution from monolith to microservices, detailing core components like service discovery, circuit breakers, gateways, and observability, while stressing that adoption must be driven by business complexity and team needs — not service count — and provides a practical checklist for splitting and transformation.
API GatewayCircuit BreakerConfiguration Center
0 likes · 10 min read

This article traces software architecture evolution from monoliths through primitive distributed systems, SOA, microservices, and cloud-native, highlighting two recurring patterns — finer decoupling and stronger fault isolation — and a shift from zero-failure goals to designing for resilience, while outlining four unprecedented challenges AI agents introduce: semantic hallucinations, stateful context, dynamic orchestration, and observability gaps.
AI agentscloud-nativedistributed systems
0 likes · 23 min read

Firebolt consolidated previously independent metadata, identity, and garbage-collection services into its core database process to simplify multi-environment deployment and reduce cross-service coordination, while analyzing trade-offs in fault isolation, resource contention, and the distinction between module and process boundaries.
Database ArchitectureFault IsolationFirebolt
0 likes · 10 min read

The article analyzes how the hidden costs of microservices, the rise of AI‑augmented solo developers, and economic pressure are driving a shift back toward modular monoliths and lightweight Java frameworks, exemplified by the open‑source Feat project.
AIJavabackend architecture
0 likes · 11 min read

The Twilio Segment team migrated their server‑side event‑forwarding infrastructure from a sprawling microservice architecture to a single monolithic service, detailing the performance bottlenecks, operational overhead, testing challenges, trade‑offs, and productivity gains that drove the decision.
backend architectureevent forwardingmicroservices
0 likes · 15 min read

The article explains why monolithic architecture is the optimal choice for early‑stage, low‑traffic projects due to its speed, simplicity, and low overhead, but later suffers from release coupling, resource contention, and team conflicts, outlining clear criteria for when to migrate to microservices.
deploymentmicroservicesmonolith
0 likes · 3 min read


ZhiKe AIJun 11, 2026 · Backend Development
The article argues that monolithic architecture is not inherently flawed; the real issue is a “big ball of mud” lacking clear module boundaries, and it explains how the MonolithFirst principle, an architecture spectrum, modular‑monolith design rules, and real‑world case studies guide teams to choose the right structure.
case studymicroservicesmodular monolith
0 likes · 13 min read

The article argues that microservices are often over‑hyped, add significant complexity and operational cost, and contribute little to a company's success, making them unsuitable for most small‑team or low‑traffic projects while suggesting a modest 80% monolith‑20% microservice split for rare high‑reuse cases.
Complexityarchitecturemicroservices
0 likes · 9 min read

The article explains that scaling a monolithic app can handle traffic, but microservices are needed when core services are affected by edge modules, team collaboration suffers, or resource‑intensive tasks cause configuration conflicts, outlining clear signals and trade‑offs for each approach.
microservicesmonolithresource management
0 likes · 10 min read

This article explains why microservices, while attractive for large systems, introduce hidden costs, operational complexity, network latency, data management challenges, and testing difficulties, and provides a decision framework to determine when a monolith‑first approach is more appropriate.
backend architecturemicroservicesmonolith
0 likes · 15 min read

This article enumerates twenty essential Java and Spring Boot architecture patterns—from monoliths and layered designs to microservices, event‑driven, cloud‑native, and AI‑driven systems—explaining their structure, typical use cases, advantages, drawbacks, and when to choose each for building stable, fast, and scalable applications.
Spring Bootarchitecturecloud-native
0 likes · 11 min read

Shopify handles over 30 TB of data each minute and millions of requests by using a disciplined, modular monolithic architecture enhanced with hexagonal design, Pods isolation, real‑time data pipelines, and a heavily sharded MySQL deployment, demonstrating that simplicity can scale to internet‑level traffic without microservices.
databaseshexagonal-architecturemonolith
0 likes · 10 min read

After years of hype, many leading firms such as Amazon, Alibaba, and Google are reverting to monolithic architectures, exposing the hidden operational, performance, and maintenance costs of microservices and highlighting when a single, well‑structured codebase can be more efficient and manageable.
Backendmicroservicesmonolith
0 likes · 10 min read

The article recounts a startup’s painful experiment with 47 microservices, exposing hidden operational costs, deployment delays, and outage risks, and ultimately shows how consolidating back to a well‑structured monolith dramatically improved performance, cost, and delivery speed.
architecturecloud-nativemicroservices
0 likes · 8 min read

The article examines how many leading companies that once championed microservices are now reverting to monolithic architectures, explains the hidden complexities microservices introduce, compares the practical benefits of monoliths, and outlines scenarios where each approach makes sense, urging teams to choose the architecture that best fits their scale and workflow.
monolithsoftware architecturesystem design
0 likes · 7 min read


21CTOJan 26, 2025 · Artificial Intelligence
The article examines Trump’s executive order on TikTok, the platform’s demand to sell half its equity to a U.S. entity, and delves into the sophisticated AI‑driven recommendation algorithms—highlighting the Monolith real‑time system, online training, and research that explain TikTok’s addictive success.
AIAlgorithmReal-time Training
0 likes · 8 min read

The article traces software architecture from early distributed systems through monoliths, SOA, microservices and serverless, explaining why each paradigm arose, the trade‑offs they entail, and how to decide between monolith and microservices based on team size, expertise, organizational structure, and business needs.
distributed systemsmicroservicesmonolith
0 likes · 25 min read

Tencent Docs tackles the trade‑offs of monolithic and microservice architectures by implementing a flexible, automated system that merges selected microservices into a few monoliths for private‑cloud scenarios, reducing runtime costs, deployment overhead, image size, memory usage and CPU consumption while preserving performance and scalability.
architecturedeploymentmicroservices
0 likes · 14 min read


ITPUBOct 5, 2024 · Backend Development
This article explains how Tencent Docs tackled the high runtime, deployment, and image‑distribution costs of a large microservice fleet by building a flexible architecture that can merge selected services into a few monolith binaries for private deployments, while retaining microservices for public scenarios, and shares the tooling, configuration, challenges, and performance gains achieved.
BackendConfigurationarchitecture
0 likes · 15 min read

In 2023, leading tech firms like Google and Amazon publicly questioned the microservice paradigm, revealing performance, cost, and complexity drawbacks, and showcasing a shift toward monolithic or runtime‑driven architectures that promise lower latency, reduced expenses, and simpler scaling.
cloud-nativemonolithsoftware architecture
0 likes · 11 min read

In 2023, leading cloud giants like Google and Amazon publicly questioned the value of microservices, presenting new “Microservices 2.0” principles and monolithic alternatives that promise dramatically lower latency, cost, and operational complexity while reshaping backend architecture debates.
cloud-nativemicroservicesmonolith
0 likes · 12 min read

2023 saw a wave of high‑profile tech leaders—Google’s engineers, Amazon Prime Video, and DHH—questioning the microservices paradigm, presenting data‑driven case studies that show dramatic latency and cost reductions when moving to monolithic or runtime‑managed architectures, and urging architects to reassess scalability versus complexity trade‑offs.
Cost Optimizationarchitecturecase study
0 likes · 12 min read

In 2023, leading tech companies like Google and Amazon publicly criticized the microservices model, presenting new architectural approaches that combine logical monoliths with automated runtimes, dramatically cutting latency and cost while prompting many other firms to abandon microservices in favor of simpler, more efficient monolithic designs.
Cost Optimizationarchitecturecloud-native
0 likes · 11 min read

In 2023, major tech companies such as Google and Amazon publicly questioned the benefits of traditional microservice architectures, presenting new "microservice 2.0" concepts, monolithic alternatives, and cost‑performance analyses that highlight a broader industry shift toward more pragmatic, cloud‑native design approaches.
Cost Optimizationarchitecturecloud-native
0 likes · 12 min read

Over‑engineering with micro‑services creates needless complexity, high costs, and fragile systems, as many startups and developers adopt them for hype rather than scale, while successful companies like Dropbox and Netflix began as monoliths and thrive, proving that simple, well‑designed architectures usually outweigh distributed solutions.
monolithsoftware architecture
0 likes · 9 min read

In 2023, leading tech firms such as Google, Amazon, Uber and others began questioning the dominance of microservices, presenting new architectural approaches that combine logical monoliths with runtime‑driven deployment, promising dramatically lower latency, cost reductions and simpler operations.
AmazonGooglecloud-native
0 likes · 10 min read

Facing low development efficiency, poor CPU utilization, and fragile fault tolerance, the QQ Browser content ingestion team rebuilt a 93‑service microservice system into a single‑process, plugin‑driven architecture, achieving up to 13‑fold throughput gains, 10‑fold batch‑processing speedups, and dramatically reduced lead times and code complexity.
BackendC++CI/CD
0 likes · 22 min read


21CTODec 31, 2023 · Backend Development
Prime Video’s engineers detail how abandoning a costly micro‑service and serverless setup for a streamlined monolithic architecture on EC2/ECS cut infrastructure expenses by over 90 % while boosting scalability, challenging the prevailing cloud‑native hype.
AWSCloud Cost Optimizationmicroservices
0 likes · 6 min read


21CTODec 27, 2023 · Cloud Native
2023 saw a growing backlash against microservices as major players like Google, Amazon, and Basecamp’s DHH highlight performance, cost, and complexity issues, proposing monolithic or “microservices 2.0” approaches that promise lower latency, reduced expenses, and simpler deployment, sparking a re‑evaluation of cloud‑native architectures.
architecturecloud-nativecost
0 likes · 12 min read

This article details how Tencent Docs implements a flexible architecture that can switch between monolithic and microservice deployments, describing the motivations, such as framework diversity, configuration conflicts, global variable management, hidden bugs, the custom 'monolith' tool with its configuration format, and the resulting performance and resource savings.
architecturemicroservicesmonolith
0 likes · 15 min read

Tencent Docs built a configurable “monolith” tool that merges selected tRPC‑Go microservices into a few monolithic modules for private‑cloud deployments, overcoming framework, configuration, global‑state, and bug‑resolution challenges, and achieving up to 75 % image‑size reduction and 96 % memory savings while preserving microservice advantages where needed.
Configurationarchitecturecloud
0 likes · 15 min read

This article explains how the team transformed a Go‑based microservice recommendation system into a single‑pod monolithic application using tRPC‑Go, detailing performance bottlenecks, code‑level mock‑proxy techniques, deployment adjustments, and the resulting dramatic reduction in CPU consumption.
BackendGocloud-native
0 likes · 13 min read


ITPUBDec 1, 2023 · Backend Development
This article explains how a large‑scale recommendation system built with tRPC‑Go microservices was refactored into a single‑process monolith to cut network overhead, reduce CPU usage by over 60%, and retain the benefits of microservice development while minimizing code changes.
GoProxymicroservices
0 likes · 14 min read

The article reflects on the promises and pitfalls of microservices, comparing them to monolithic architectures, and shares practical lessons about scalability, deployment complexity, data consistency, and when a monolith might actually be the better choice.
DevOpsbackend architecturemicroservices
0 likes · 11 min read


LouZaiNov 21, 2023 · Backend Development
This article walks through the step‑by‑step evolution of an online supermarket from a simple monolithic web app to a fully split microservice architecture, highlighting the problems encountered, the rationale for each refactoring decision, and the essential components such as service isolation, messaging, monitoring, tracing, gateway, service discovery, circuit breaking, testing, and service mesh.
Circuit BreakerDistributed TracingService Discovery
0 likes · 22 min read

The article shows how to monolithize selected tRPC‑Go microservices by defining protobuf‑generated Go interfaces and swapping RPC proxies for in‑process implementations via a proxy API, cutting CPU usage by 61% while keeping microservice flexibility and offering best‑practice guidelines for Go service design.
Gocloud-nativemicroservices
0 likes · 13 min read

An in‑depth analysis of Amazon Prime Video’s monitoring service reveals how the team abandoned a costly serverless micro‑service architecture in favor of a streamlined monolith on EC2/ECS, cutting infrastructure expenses by over 90% while improving scalability, prompting industry leaders to reassess cloud‑native design assumptions.
AWSCost Optimizationarchitecture
0 likes · 11 min read

The Prime Video engineering team replaced a costly, scaling‑limited serverless microservice architecture with a streamlined monolithic solution on EC2/ECS, achieving more than a 90% reduction in infrastructure expenses while improving scalability, sparking widespread debate about the true value of microservices and serverless approaches.
AWSCost Optimizationbackend architecture
0 likes · 11 min read

A detailed case study reveals how Amazon Prime Video replaced a costly, serverless micro‑service monitoring system with a streamlined monolithic architecture on EC2/ECS, slashing infrastructure expenses by over 90 % and sparking a broader debate on the true merits of microservices versus monoliths.
Cost Optimizationcloud computingmicroservices
0 likes · 10 min read

A Prime Video case study shows that moving from a costly serverless micro‑service architecture to a streamlined monolith on EC2/ECS reduced infrastructure expenses by over 90% while improving scalability, sparking a heated debate about the true value of microservices and serverless in large‑scale video streaming.
AWSCloud ArchitectureCost Optimization
0 likes · 11 min read

This article explains why and how to decompose large or legacy applications into microservices using business‑capability and sub‑domain (DDD) approaches, outlines their benefits, discusses common challenges such as latency and data consistency, and introduces the Strangler pattern for gradual migration.
business capabilitydecompositiondomain-driven design
0 likes · 7 min read

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.
business capabilitymonolithservice decomposition
0 likes · 6 min read

This article details GitHub’s 12‑step journey from a 12‑year‑old Ruby on Rails monolith to a modular microservices architecture, covering rapid growth, data partitioning, service extraction, operational shifts, and resilient design principles to empower developers while maintaining product value.
Data PartitioningGitHubbackend architecture
0 likes · 16 min read

This article examines the common perceived benefits of microservices, shows how many of them can be achieved with a well‑designed monolith, and provides concrete criteria and tactics for small, medium, and large teams to decide which architecture best fits their context.
Dependency Managementmicroservicesmonolith
0 likes · 13 min read

This article examines layered monolithic architecture styles, comparing classic four‑layer designs with five‑layer variants, discussing their benefits, trade‑offs, impact on complexity, change isolation, and how modular thinking can bridge the gap between technical layers and business domains.
BackendLayered Architecturemodularization
0 likes · 12 min read

This article explains the concepts of software architecture, compares monolithic and distributed styles, and walks through a real‑world inventory system migration—including functional and business splitting, CQRS adoption, and distributed transaction challenges—illustrated with Java code examples.
Javaarchitecturecqrs
0 likes · 17 min read

This article explains what software architecture is, why choosing an architectural style matters, compares monolithic and distributed approaches using a real‑world inventory system case study, and details the step‑by‑step functional and business splitting, CQRS implementation, code refactoring, and handling of distributed transactions.
cqrsdistributed systemsmicroservices
0 likes · 20 min read

The article argues that launching a brand‑new project using microservices often incurs excessive infrastructure, cultural, and operational costs that outweigh the touted benefits, and suggests that a well‑designed modular monolith can be a more pragmatic alternative for many teams.
Fault IsolationOperationsdeployment
0 likes · 13 min read


21CTOMar 16, 2022 · Backend Development
This article traces Airbnb's architectural journey from a single‑Ruby‑on‑Rails monolith through a microservices era to its current hybrid micro‑macro service model, highlighting the motivations, challenges, and engineering practices that shaped each transition.
AirbnbBackendarchitecture
0 likes · 6 min read

The article explains how microservices differ from monolithic applications by emphasizing team‑based, autonomous service design, data‑sharing challenges, dependency management, API communication patterns, and the use of shared caches to improve performance and reliability.
Cachingmicroservicesmonolith
0 likes · 7 min read

The article explains how microservices differ from monolithic applications, discusses the challenges of data sharing and service dependencies, and offers practical approaches such as one‑way dependencies, aggregation services, HTTP API design, and using a shared Redis cache to improve performance and reliability.
backend architecturedata sharingmicroservices
0 likes · 8 min read

This article explains the fundamental definition of software architecture, distinguishes systems, subsystems, modules, components, frameworks, and various architecture layers, and examines how architectures evolve from monoliths to distributed services and micro‑services while highlighting common pitfalls and evaluation criteria.
Architecture PatternsLayered Architecturedistributed systems
0 likes · 23 min read


phodalFeb 28, 2022 · Backend Development
The team behind the open‑source ArchGuard platform recounts their migration from Maven to Gradle, library updates, and a surprising shift from a microservice‑based system to a monolithic architecture, explaining the challenges of legacy services, the principles guiding service granularity, and the practical benefits of a single‑code‑base deployment for a small open‑source project.
DDDmigrationmonolith
0 likes · 8 min read

This article explains the essence of software architecture, covering definitions, system vs. subsystem, module vs. component, framework vs. architecture, various architectural layers, classifications, evolution from monolith to microservices, and how to evaluate a design’s suitability for business and non‑functional requirements.
Design Principlesmicroservicesmonolith
0 likes · 26 min read

This comprehensive guide explains the essence of software architecture, its layers and classifications, architectural levels, strategic versus tactical design, evolution from monoliths to micro‑services, common pitfalls, and key metrics for evaluating a sound architecture.
Architecture PatternsBest Practicesdistributed systems
0 likes · 22 min read

This article explains the evolution from monolithic applications to microservices, outlines the advantages and disadvantages of both architectures, and provides practical guidance on when and how teams should adopt microservices to improve agility, scalability, and organizational efficiency.
AgileDevOpsarchitecture
0 likes · 14 min read

This article explains the evolution from monolithic applications to microservices, detailing their principles, benefits, drawbacks, design considerations, and the three-step implementation process, while highlighting the impact on agile development, DevOps culture, technology stacks, and organizational structure.
cloud-nativemonolithsoftware engineering
0 likes · 13 min read

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".
Conway's Lawmonolithscalability
0 likes · 11 min read

This article compares microservices and monolithic architectures across eight operational dimensions—network latency, complexity, reliability, resource usage, scaling precision, throughput, deployment time, and communication—showing where each approach excels and concluding which wins overall.
Operationsarchitecturemicroservices
0 likes · 12 min read

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.
architecture evaluationdeploymentmicroservices
0 likes · 17 min read

This article explains the fundamental concepts of software architecture, including definitions of systems, modules, frameworks, various architectural layers such as business, application, data, code, technical and deployment, and discusses the evolution from monolithic to distributed and microservice architectures along with evaluation criteria and common pitfalls.
application layersmicroservicesmonolith
0 likes · 20 min read

This article compares monolithic applications and microservice architectures across dimensions such as network latency, development and operational complexity, reliability, resource consumption, scaling precision, throughput, deployment speed, and team communication, highlighting where each approach wins and offering guidance on when to adopt microservices.
architecturelatencymicroservices
0 likes · 12 min read

This article explains the hierarchical architecture levels, contrasts strategic and tactical design, and walks through the evolution from monolithic applications to distributed services and micro‑services, highlighting benefits, drawbacks, and key metrics for evaluating a sound system architecture.
distributed systemsmicroservicesmonolith
0 likes · 11 min read


ITPUBMar 6, 2020 · Backend Development
Segment’s engineering team recounts their evolution from a simple monolith to a sprawling micro‑service ecosystem and back again, detailing queue bottlenecks, repo fragmentation, shared‑library chaos, and how consolidating everything into a single codebase restored performance, scalability, and developer productivity.
Backendmicroservicesmonolith
0 likes · 16 min read

The article recounts Segment's journey from a monolithic system to a sprawling micro‑service architecture, the operational pain points that emerged, and how consolidating over 140 services into a single codebase improved testing speed, deployment simplicity, and overall developer productivity while revealing new trade‑offs.
Backendmonolithqueues
0 likes · 16 min read

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.
GoProtobufRPC
0 likes · 10 min read

This article explains why monolithic applications become unmanageable as they grow, outlines the advantages of breaking them into independent microservices, and discusses the architectural, operational, and testing challenges that accompany a microservice‑based design.
architecturedeploymentmicroservices
0 likes · 16 min read

This article walks through the evolution from traditional three‑layer monolithic architecture to microservice architecture, explaining system design concepts, the drawbacks of monoliths, the benefits and challenges of microservices, and compares them with SOA, providing clear diagrams, pros and cons, and practical insights for backend engineers.
SOAbackend architecturemicroservices
0 likes · 15 min read


21CTONov 18, 2015 · Backend Development
This article explains why microservices outperform monolithic architectures by detailing their design, deployment, benefits, and challenges, helping developers decide if the approach suits complex, evolving applications; it also compares traditional single‑code‑base models, discusses scaling strategies, and outlines practical considerations for implementation.
Backendcloud-nativemicroservices
0 likes · 17 min read
