service boundaries

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.

Bounded ContextMicroservicesarchitecture

0 likes · 20 min read

Designing Microservices with Domain‑Driven Design and Bounded Contexts

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.

Bounded ContextMicroservicesbackend architecture

0 likes · 19 min read

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

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.

BackendMicroservicesisolation

0 likes · 17 min read

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

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.

MicroservicesRPCSSO

0 likes · 10 min read

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