Leo Jung
RSS FeedI’m Leo Jung, a software engineer interested in backend systems, software design, and architecture.
This blog is where I write about what I learn, build, and think through as a developer.
Recent Posts
-
[DDD Intro #30] My understanding of DDD: Good design starts from good questions
When first encountering DDD, the terminology appears first. Entity, Value Object, Aggregate, Repository, Domain Service, Domain Event, Bounded Context, Context Map. If CQRS, Event Sourcing, Hexagonal Architecture, and Microservice follow, DDD feels like a huge technical system.
-
[DDD Intro #29] DDD adoption checklist
DDD is a powerful approach, but it is not needed for every problem. It can greatly help complex domains, but applying it excessively to a simple CRUD system can only increase cost.
-
[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 #27] Applying DDD to legacy systems
When studying DDD, we see many clean examples. Domain objects are clear, layers are separated, and Aggregate boundaries are well defined. But real systems are often not like that.