AI Briefing#oliveyoung
The latest AI and developer news about #oliveyoung, with the original source and a short summary.
The latest AI and developer news about #oliveyoung, with the original source and a short summary.
To solve API latency issues arising from SDUI adoption, Oliveyoung introduced a dual caching strategy using Caffeine and Redis, improving response speed to under 1ms.
Oliveyoung gradually migrated a hard-to-maintain, roughly 7,000-line PL/SQL procedure to a Java-based module using the Strangler Pattern.
Oliveyoung conducted a PoC using Module Federation to improve its large-scale frontend architecture.
An Oliveyoung iOS engineer introduces a custom developer mode built with SwiftUI to improve debugging efficiency in a hybrid app environment.
Oliveyoung's Order & Payment Squad reduced human errors and improved collaboration culture by introducing KPT retrospectives and a PR template.
The Oliveyoung Tech Team shares a case study of introducing a PWA to overcome constraints in the logistics field, improving the UX of a PDA-based WMS.
Oliveyoung built an API test automation system to solve data inconsistency issues caused by the transition to a real-time message-based system.
Oliveyoung introduces the phased test strategy it applied while building GMS, its global WMS, using a big bang deployment approach.
Olive Young built its own block-based CMS in-house, reducing content production time from 7 days to 20 minutes and implementing a framework-independent editor.
Olive Young participated in SpringCamp 2025 as a Gold sponsor, presenting logistics system improvement case studies and engaging with developers.
Olive Young maximized logistics efficiency by integrating online and offline inventory and building a message-based OMS.
Oliveyoung has revealed how it operates its squad organization and collaboration process, optimized for its MSA structure.
This covers the technical challenges and solutions Olive Young faced while building its own Kafka-based global logistics system (GMS) without relying on external solutions.
Oliveyoung introduced a Kafka-based asynchronous request-response architecture to resolve performance degradation issues in its existing synchronous order system.
Oliveyoung proposes a 4-stage scaling automation strategy that overcomes the limitations of existing Auto Scaling to respond to rapid traffic spikes.
A newly onboarded QA engineer with a background as an iOS developer shares the 5-month growth and onboarding experience at Oliveyoung.
Oliveyoung has adopted chaos engineering, which intentionally induces failures to test system resilience, in order to improve service stability.
To overcome the limitations of existing attribute-based similarity calculations, Oliveyoung developed a semantic product similarity model that leverages user search logs.
This shares a case of building an efficient quality management system in a resource-limited solo QA environment by defining a user-perspective happy path and separating test environments.
Olive Young cut app review reception lead time by 50% by directly leveraging store APIs instead of an external platform's crawling method.
Oliveyoung shares the design experience of expanding the store domain, separated via DDD, into online and offline customer-facing services.
Olive Young's iOS development team operated a booth at the Let'Swift 2024 conference to communicate with developers and raise brand awareness.
Olive Young Global Mall introduced address autocomplete and verification features to solve the problem of shipping holds caused by address entry errors.
Introduces the architecture and implementation strategy Oliveyoung adopted to modernize its legacy store domain based on DDD tactical design.