1、Modernising in healthcareFrom on-prem to the cloudA case studyLeander VanderbijlSisyphusAmazonWhat is MJog?Batch MessagingEMR IntegrationsAppointment RemindersQuestionnairesPatient Relationship ManagementCrossing the chasmChoosing cloud migration Designing the architecture Implement cloud native ser
2、vices Observability Defining requirementsMJog ArchitectureMJog Communication PatternsWhats on fire?Too many feature requests Patchwork of techs,libs and frameworks Everything was built around being on-prem 15+years of tech debt Post Covid,everyone wants cloud software Primary developer leavingEveryt
3、hing is on fireWhat are our biggest risks?The application was a patchwork of techs,libs and frameworksPractices threatening to leave if there is no cloud versionThe UX is stuck in 2004No new features in years15+years of tech debtThe developer who built the system was leaving in 9 monthsNow what?A se
4、parate ec2 for every customer Standard on-prem installationCloud native services for syncs and data access Refactor the web app to work against any tenantLift n ShiftCloud rewrite6-9 month time frame Much cheaper Doesnt solve our contract renewal problem1-2 month time frame Lose money on every insta
5、llation Doesnt solve our lack of knowledge problemBeing pragmaticSometimes there is no solution that fits all the requirements-doing multiple things is an option Take the time to really understand the problem and options-regardless of urgency Remember,at the end of the line,its our customerCrossing
6、the chasmChoosing cloud migration Designing the architecture Implement cloud native services Observability Defining requirementsRedesigning for cloud nativeUnderstand what we have Identify domains and areas of functionality Design the implementationWhat functionality do we have?Messaging syncEMR Syn