We will be performing a major upgrade to AgileMD's core Web (HTTP) API and conducting a large database migration. We expect the observed outage to last between 1 and 3 hours.
To enable a host of planned platform and application upgrades, we are moving much of the primary account and content data into a bigger, more performant database. In addition, we are expanding the capabilities of the AgileMD Web API to service growing needs of our mobile and EHR-integrated customers. We currently service about 500k requests per day and expect to be well over 1M per day by year's end.
Normally, our team deploys code on a continuous basis. Almost every day, one application or another receives a production upgrade; new features and bug fixes are safely released without any downtime. However, this change is much larger and much more complex. Like any good flight-plan, we have developed a detailed checklist and tested the migration many times in our QA (quality assurance) environment. At several points during the execution of that checklist we must halt all inbound requests to avoid data corruption. At these points, downtime is unavoidable – new accounts cannot be created, resources cannot used within the EHR, and all mobile apps will stop syncing resource changes. So, during the maintenance window, we ask that you sit back, avoid changing your content and department settings, and wait for the all clear from us. If you must make an emergency change (for example, a critical pathway must start order a new drug), please contact your account representative or email us at email@example.com
– we will have extra team members available to manage emergency issues on a case-by-case basis.