Tag: Architecture
All the articles with the tag "Architecture".
-
[DDD Intro #28] Modular Monolith: What to think about before microservices
As a system grows, we start wanting to split services. It feels like creating independent services for orders, payments, members, notifications, and settlement will make things cleaner. It seems each team can own its service, deploy independently, and isolate failures.
-
[DDD Intro #25] Microservice and DDD: Is a Bounded Context a service?
When talking about DDD, microservices often appear together. The picture of splitting Bounded Contexts, making each context a service, and giving each independent deployment and an independent database is attractive.
-
[DDD Intro #24] Event Sourcing is not required for DDD
After learning Domain Event, we naturally encounter Event Sourcing. If we express things that happened in the domain as events, storing events instead of state may look better.
-
[DDD Intro #23] CQRS: When to separate read models and write models
When studying DDD, we often encounter the word CQRS. So it is easy to think that proper DDD requires CQRS, and that CQRS requires Event Sourcing.
-
[DDD Intro #20] Hexagonal Architecture: A structure that places the domain at the center
Layered Architecture is an important starting point for protecting the domain model. But in real code, even when layers appear to flow in one direction, the domain is often still strongly tied to frameworks or databases.
-
[DDD Intro #19] Layered Architecture: Protecting the domain layer
When we try to implement DDD, architecture soon enters the conversation. Names such as Presentation Layer, Application Layer, Domain Layer, and Infrastructure Layer appear. We split packages, decide dependency direction, and separate responsibilities by layer.