Continuous delivery model
Genesys Cloud products use the continuous delivery model in a microservices architecture. Instead of releasing large batches of changes two or three times a year, we continuously release small batches of changes as we make them. When a change meets our quality standards, we push that change to production. To ensure product quality and resiliency, tens of thousands of automated tests are run daily, including chaos testing. To avoid versioning dependency, changes are both backward- and forward-compatible. A tested rollback plan is always in place to ensure immediate rollback if problems are detected.
Development teams schedule higher risk changes during non-peak hours with attempts to limit or avoid during holidays and seasonal peak periods. Development teams post a maintenance message on the Genesys Cloud System Status page if a change might cause downtime or degradation for users.
In addition to allowing the deployment of small batches of changes as needed, without interrupting the user experience, the continuous delivery model gives Genesys Cloud the flexibility to quickly develop, test, and release:
- Usability enhancements — The User Experience team is always looking for new ways to make Genesys Cloud more useful and easier to use.
- Patches — Engineering and Quality Assurance teams work together to keep the products running smoothly.
- Security updates — The Information Security team stays vigilant of the evolving threats in cyberspace and adjusts our defensive strategy as needed, when needed.
- Resource Center updates — The Documentation team updates Resource Center content every week.
For our customers, continuous delivery means that no one is locked into a specific version. When you subscribe to our service, you get the latest version, and you continue to have the latest version throughout the life of your subscription.
For more information, see Benefits of continuous integration-continuous deployment (CI-CD).
