Skip to content
Tagged articles

service granularity

7 articles · Page 1 of 1
IT Architects Alliance
IT Architects Alliance
Oct 20, 2026 · R&D Management

Why Segment Merged 140+ Microservices: The Hidden Costs of Service Granularity

Segment consolidated over 140 microservices into a monolith to reduce change fan-out and operational burden, while Prime Video moved video frame processing in-memory to eliminate 14.4 million hourly object storage handoffs; both cases show service boundaries must justify their cost in coordination, data transfer, and failure isolation.

architecture trade-offschange fan-outdata handoff
0 likes · 15 min read
Why Segment Merged 140+ Microservices: The Hidden Costs of Service Granularity
Code Archaeology
Code Archaeology
Aug 17, 2026 · Backend Development

Microservices Architecture Explained: Patterns, Trade-offs, and Team Topologies

This article provides a comprehensive overview of microservices architecture, covering bounded contexts, service granularity, API layers, sidecar/service mesh patterns, communication styles, data topology, distributed transactions with Saga, common anti-patterns, characteristic ratings, and team topology alignment.

Bounded ContextSaga patterndatabase-per-service
0 likes · 23 min read
Microservices Architecture Explained: Patterns, Trade-offs, and Team Topologies
Thought Artisan
Thought Artisan
Aug 8, 2026 · Fundamentals

Why Software Architecture Is Hard: 8 Core Trade-offs from 'The Hard Parts'

This article reviews 'Software Architecture: The Hard Parts', highlighting eight key architectural challenges including trade-offs, data-architecture tensions, service granularity, database decomposition, distributed data access, contract design, code reuse, and error handling in distributed systems.

Distributed Systemscontract designdatabase decomposition
0 likes · 7 min read
Why Software Architecture Is Hard: 8 Core Trade-offs from 'The Hard Parts'
Mike Chen's Internet Architecture
Mike Chen's Internet Architecture
Oct 31, 2025 · Backend Development

Microservices vs SOA: Key Differences Every Backend Engineer Should Know

This article compares microservices and SOA, covering design philosophy, service granularity, autonomy, communication mechanisms, and deployment/operations, highlighting how microservices favor lightweight protocols, independent deployment, and container orchestration, while SOA relies on centralized middleware and coarse‑grained services.

Backend ArchitectureSOAcommunication protocols
0 likes · 4 min read
Microservices vs SOA: Key Differences Every Backend Engineer Should Know
JD Tech
JD Tech
Jun 6, 2024 · Operations

Analyzing Service Granularity and Consolidation in Promise Microservices

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.

Backend Architectureservice granularityservice splitting
0 likes · 17 min read
Analyzing Service Granularity and Consolidation in Promise Microservices
Programmer DD
Programmer DD
Sep 25, 2017 · Backend Development

Avoid These Common Microservice Pitfalls: Granularity, Trend‑Chasing, and Contract Traps

The article examines typical microservice anti‑patterns—including overly fine or coarse service granularity, blindly following trends, and static contract versioning—explains why they occur, illustrates each with diagrams and code snippets, and offers practical guidance for making balanced architectural decisions.

architecture pitfallscontract versioningservice granularity
0 likes · 9 min read
Avoid These Common Microservice Pitfalls: Granularity, Trend‑Chasing, and Contract Traps