Continuous Deployment allows CaféX to share our latest features in a fast and reliable way. Typically, changes are small but frequent, significantly decreasing the risk of migration for our customers when new versions become available.
CaféX uses a rapid deployment pipeline, enabling us to share our latest software in a stable and repeatable fashion. Whether developing new features or fixing problems, our customers receive updates in the most timely manner.
To make preparing for updates easy, we deploy the Meetings API across multiple software streams. This allows our customers:
- To arrange things ahead of the upcoming changes.
- To carry out critical operational procedures long before any changes affect their end users.
- To use this time to update any training material.
- To send any product announcements that they deem necessary.
CaféX Meetings is deployed across the following streams:
- API-Main Stream
- Provides a stream for your production applications to run against.
- All of your end users use this stream.
- Typically updates every week, two weeks later than the API-Preparatory Stream.
- API-Preparatory Stream
- Provides you with an opportunity to prepare ahead of the API-Main Stream.
- Typically updates every week, with the Knowledge Base documenting the features.
- Latest Stream
- Provides the very latest software deployment.
- Changes can occur rapidly and without notice.
- Shortest possible update cadence.
When a new deployment is sent to the API-Preparatory Stream, we:
- Update our Knowledge Base, providing you with further details.
- Create a new roundup note listing all of the important changes since the last update, and informing you of what is now in the API-Main Stream.
See: Meetings Roundup
- We recommend that you Follow the roundup section, to receive email notifications of changes to the streams.
- If you are not using the Meetings API, and instead use the CaféX Meetings application, you may see features that are ahead of the API-Preparatory stream.
Each week, CaféX reviews the available deployments and, when appropriate, chooses to send a deployment to the API-Preparatory Stream. Two weeks later, the same deployment is sent on the API-Main Stream.
Remember that the incremental changes to Meetings deployments are small. It is probable that your users are not affected directly by the modifications on a week-by-week basis. You enable any new features with your account settings, meaning that you are in control of your users' experience.
So that you may prepare effectively during holiday periods, the streams may not update until the typical routine resumes.
Managing Critical Issues
Realistically, even with the introduction of a preparatory stream, CaféX understands that critical issues can affect either of the deployment streams. If necessary, CaféX can roll back or accelerate the API-Preparatory or API-Main streams.