AI Briefing#domain-driven-design
The latest AI and developer news about #domain-driven-design, with the original source and a short summary.
The latest AI and developer news about #domain-driven-design, with the original source and a short summary.
Analyzed an NPE incident in production and proposed design principles using Optional and domain objects to structurally prevent null errors.
Yeogieotae used Spring Modulith to enforce module boundaries and event flows in code.
Airbnb rolled out more than 20 local payment methods worldwide in 14 months through payments platform modernization and a modular architecture.
KakaoBank shares its experience of grappling with domain boundary separation and applying Spring Modulith while transitioning a legacy monolith to MSA.
Kakao Pay shares the process of internalizing its credit core system by applying DDD to efficiently manage its complex credit business.
Oliveyoung shares the design experience of expanding the store domain, separated via DDD, into online and offline customer-facing services.
A hands-on adaptation story of settling into a new team by learning a codebase built on Scala, ZIO, and DDD.
Separating the loan comparison DB from the credit management service reduced load and coupling.
They analyzed the domain using Event Storming and designed the architecture based on aggregates and domain events.
The Outbound Service Development Team resolved technical debt by introducing pair programming and a standardized development system.
The article details how domain experts and developers work together through Event Storming to identify problems and design aggregates.
The author shared their experience of overcoming the limitations of DB-centric development by practicing DDD and integrating object-oriented principles with cloud infrastructure.