BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.coscup.org//coscup-2026//talk//8RZ3ZV
BEGIN:VTIMEZONE
TZID:CST
BEGIN:STANDARD
DTSTART:20000101T000000
RRULE:FREQ=YEARLY;BYMONTH=1
TZNAME:CST
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-coscup-2026-8RZ3ZV@pretalx.coscup.org
DTSTART;TZID=CST:20260808T123000
DTEND;TZID=CST:20260808T124500
DESCRIPTION:At Remember (a career networking platform in Korea)\, our notif
 ication service had been running on a legacy Ruby-based architecture for y
 ears.\n\nAs the number of users and notification channels grew\, we starte
 d facing challenges in scalability\, maintainability\, and operational com
 plexity. The system had accumulated technical debt\, making it increasingl
 y difficult to introduce new features and ensure reliable delivery.\n\nIns
 tead of performing a risky big-bang migration\, we gradually rebuilt the n
 otification platform as Java-based microservices while continuing to serve
  production traffic.\n\nIn this talk\, I will share:\n- Why we decided to 
 migrate from Ruby to Java\n- How we decomposed the existing architecture\n
 - Strategies for running old and new systems in parallel\n- Challenges aro
 und message delivery\, consistency\, and monitoring\n- Lessons learned fro
 m operating the migration in production\n\nThis session focuses on practic
 al engineering decisions rather than theory\, providing insights that team
 s can apply when modernizing long-running systems.
DTSTAMP:20260713T142503Z
LOCATION:TR412-2
SUMMARY:From Ruby to Java: Migrating a Notification Platform to Microservic
 es - Sunyoung Shin
URL:https://pretalx.coscup.org/coscup-2026/talk/8RZ3ZV/
END:VEVENT
END:VCALENDAR