Oliveyoung Online Store's Display and Its Backend Journey
Key point
Oliveyoung transitioned its home screen architecture from Monolithic to MSA to handle large-scale traffic and improve development efficiency.
Details
Oliveyoung pursued a transition to MSA (Microservices Architecture) to solve the problems of limited server scaling and heavy development effort caused by complex dependencies in its existing Monolithic structure.
The new architecture separates data into two areas for serving.
- Static Data: Data provided identically to all users, ensuring fast response times through caching.
- Personal Data: User-specific customized data, managed via a separate API considering business logic and external system dependencies.
In particular, by separating the Static Data API based on data-driven analysis, the team identified the pattern of users not scrolling down to the bottom of the home screen, and optimized network and parsing costs accordingly.
Additionally, to ensure that a failure in a specific system does not lead to a complete service outage, they built CircuitBreaker and multiple Fallback logic, securing the stability to display the home screen under any circumstances.
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.