Modernizing 10 Years of Legacy - Part 1: The First Step Toward Domain Separation
Key point
This covers Oliveyoung's process of separating the store domain and establishing a DDD strategy to modernize OliveOne, its 10-year-old legacy system.
Details
Oliveyoung has struggled with legacy issues stemming from OliveOne, a back-office platform previously operated by CJ OliveNetworks, where various domains were intermixed. As the organization grew rapidly and multiple squads were formed, ownership of the store domain remained unclear, leading to problems such as squads directly referencing the DB and business logic becoming scattered.
To address these issues, the team began a modernization effort to secure ownership of the store service and clarify domain boundaries. To this end, they conducted an Event Storming workshop together with domain experts to understand the complex business flows.
Through the workshop, the following outcomes were achieved:
- Bounded Context identification: clarifying previously ambiguous scopes of work
- Domain model derivation: defining core models within each context
- Context mapping: identifying differences in meaning when a subdomain spans multiple contexts (e.g., product meta information vs. products handled by a store)
This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.
Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.