BestHub
Sign in
Tagged articles

service-boundaries

6 articles · Page 1 of 1
Data Bricklaying Diary
Data Bricklaying Diary
Aug 28, 2026 · Backend Development

Why Service Boundaries Fail: Aligning Business Rules, Data Ownership & Team Topology

This article explains why effective service boundaries require aligning business rules, data ownership, change rhythms, and team responsibilities—not just drawing boxes around nouns—using a refund processing case study to compare modular monolith vs. microservice trade-offs and verify boundaries through concrete evidence.

Domain-Driven DesignMicroservicesarchitecture-design
0 likes · 21 min read
Why Service Boundaries Fail: Aligning Business Rules, Data Ownership & Team Topology
Top Architect
Top Architect
Apr 29, 2022 · Backend Development

Designing Microservices with Domain‑Driven Design and Bounded Contexts

This article explains how microservice architecture differs from traditional service‑oriented designs, outlines its key characteristics, and shows how Domain‑Driven Design, bounded contexts, aggregates, context mapping, and event‑storming can be used to define clear service boundaries and build resilient, loosely‑coupled systems.

Domain-Driven DesignEvent StormingMicroservices
0 likes · 20 min read
Designing Microservices with Domain‑Driven Design and Bounded Contexts
IT Architects Alliance
IT Architects Alliance
Mar 17, 2022 · Backend Development

Understanding Microservices Architecture, Bounded Contexts, and Domain‑Driven Design

This article explains the principles of microservices architecture, the role of bounded contexts and domain‑driven design, and practical techniques such as context mapping, event storming, and BFF patterns for defining service boundaries, handling communication, and achieving resilient, loosely‑coupled systems.

Event StormingMicroservicesbounded-context
0 likes · 19 min read
Understanding Microservices Architecture, Bounded Contexts, and Domain‑Driven Design
ITFLY8 Architecture Home
ITFLY8 Architecture Home
Oct 8, 2021 · Backend Development

How to Define Microservice Boundaries with Domain‑Driven Design and Context Mapping

This article explains how microservice architectures differ from traditional service‑oriented designs, outlines key characteristics such as bounded contexts and autonomy, and shows how Domain‑Driven Design, context mapping, and event‑storming can be used to identify, model, and communicate clear service boundaries for resilient, scalable systems.

Event StormingMicroservicesbounded-context
0 likes · 21 min read
How to Define Microservice Boundaries with Domain‑Driven Design and Context Mapping
Top Architect
Top Architect
Apr 16, 2021 · Backend Development

When to Use Microservices: Modules, Monoliths, and Service Boundaries

The article examines the historical evolution of software modularity, explains why microservices are an extreme reaction to monoliths, discusses isolation challenges across layers, and offers practical criteria for deciding where service boundaries should be drawn in modern backend systems.

BackendSystem Designisolation
0 likes · 17 min read
When to Use Microservices: Modules, Monoliths, and Service Boundaries
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.

RPCSSObackend architecture
0 likes · 10 min read
Lessons and Reflections on Service‑Oriented Architecture and Microservice Evolution at Zhihu