#msa
The latest AI and developer news about #msa, with the original source and a short summary.
The latest AI and developer news about #msa, with the original source and a short summary.
KakaoPay Insurance safely removed legacy modules in production and laid the groundwork for a Spring Boot upgrade using an AOP-based Shadow comparison strategy.
Weights & Biases is changing its Master Service Agreement (MSA) regarding data usage and ownership.
MSA has unveiled memory sparse attention that scales up to 100M tokens.
QA directly cut off DB, cache, and queue connections to verify customer experience and post-recovery data consistency.
OpenTelemetry was introduced into a Kubernetes MSA environment to standardize logs, metrics, and traces.
Olive Young Store split its integration approach between Redis cache and Kafka events depending on data characteristics.
This is the story of building **YoungWonHee**, an internal debugging tool that ties scattered logs together into a single request flow to quickly find the root cause of exposure issues.
Yeogiyo moved the combination of multiple domain APIs into a BFF to reduce screen-level complexity.
By separating Alimtalk delivery using Spring transaction synchronization and Kafka, the team improved consistency and scalability.
Ilhaera Kim Bangsael maintained consistency with optimistic locking based on update_version.
A 4-person, 12-MSA team built role separation and Context standardization using Claude AI.
We internalized an external Batch Scheduler using Quartz and a common library, calling it OnQuartz.
Oliveyoung has revealed how it operates its squad organization and collaboration process, optimized for its MSA structure.
KakaoBank successfully split its Home service into an MSA by moving away from a legacy monolithic server and applying Hexagonal Architecture and coroutines.
Olive Young built a real-time monitoring system by integrating infrastructure metrics and business data using Datadog.
This introduces a case where the Product Squad adopted Debezium and AWS MSK Connect for data synchronization during their MSA transition.
This proposes an HTTP client design strategy that minimizes library dependencies and responds flexibly to various failure scenarios in an MSA environment.
Feature Flags decouple feature rollout from rollback to reduce the risk of Production deployments.
Oliveyoung transitioned its home screen architecture from Monolithic to MSA to handle large-scale traffic and improve development efficiency.
Oliveyoung introduced a dedicated pickup-only cart tab to improve customer accessibility, along with improvements to UI/UX and rendering.
Oliveyoung built a new inventory system leveraging Redisson and Kafka to distribute DB load and transition to MSA.
Used Kafka, Redis, and SSE to asynchronously handle high-volume traffic in financial services.
BFF simplifies WEB and Mobile APIs while CircuitBreaker prevents failure propagation.
Separating the loan comparison DB from the credit management service reduced load and coupling.