To provide better services to users, Realtime Compute for Apache Flink builds a lifecycle management system and defines the product lifecycle policy (PLP) of Realtime Compute for Apache Flink and the runtime lifecycle policy (RLP) of the engine version of Realtime Compute for Apache Flink. The lifecycle management system helps meet the increasing business requirements and increase the cloud computing efficiency by introducing new products and versions.
Scope
PLP and RLP are suitable for all service types and versions of Realtime Compute for Apache Flink. For more information about the features and release status of each service type and version, see Service types.
Description of PLP
PLP is used during the process of a service type of Realtime Compute for Apache Flink from the official launch to delivery, to End of Marketing (EOM), and finally to End of Service (EOS). PLP is used for Realtime Compute for Apache Flink only when Realtime Compute for Apache Flink has a major product change. For example, PLP is used when Blink is upgraded to Flink.
The period of time for each phase of PLP is not fixed. Before the Realtime Compute for Apache Flink team determines to conduct PLP, the team considers various factors, such as the maturity of a new service type, migration demands of users, smoothness of the migration process, and changes in costs of the new service type for users. If the team determines to conduct PLP, the team notifies users at least four months in advance. For more information, see Related services and notifications. The following figure shows the key milestones in PLP of Realtime Compute for Apache Flink.
Delisting process | Description | Precautions |
Announcement to EOM | Users are notified at least four months before the EOM phase by using a notification channel, such as announcements, internal messages, emails, or text messages. |
|
EOM to EOFS | EOM consists of the following phases:
Note The entire EOM phase cannot be less than four months. |
|
EOFS to EOS | New versions and patch versions are no longer released. Services are no longer provided, such as answering questions, resolving issues, and handling service level agreement (SLA) guarantee compensation. |
|
EOS | The product is delisted and all support services are no longer provided. | Users cannot run existing deployments or create deployments in the Realtime Compute for Apache Flink console. |
Description of RLP
Realtime Compute for Apache Flink uses the enhanced engine Ververica Runtime (VVR). For more information about the engine version planning and definition, see Engine version.
RLP is used during the process of the VVR engine in Realtime Compute for Apache Flink from the official delivery to users, to the EOM, and finally to the end of service.
The period of time for each phase of RLP is not fixed. Before the Realtime Compute for Apache Flink team determines to conduct RLP, the team considers various factors, such as the compatibility and maturity of a new version and the demands of users for version updates. If the team determines to conduct RLP, the team notifies users at least three months in advance. For more information, see Related services and notifications. The following figure shows the key milestones in RLP of Realtime Compute for Apache Flink.
If a VVR version has critical security or stability issues, we will shorten the RLP of the version to three months to avoid severe impact on business caused by this version, and notify the involved users by using the console of fully managed Flink or by sending announcements in a timely manner to upgrade the version.
Milestone | Description | Precautions |
GA | The new version can be officially released and delivered to users for use in the production environment. | None. |
EOGS | Realtime Compute for Apache Flink no longer provides new features for the engine version. | In this case, Realtime Compute for Apache Flink can no longer meet the requirements for new features and performance optimization. Realtime Compute for Apache Flink can only meet the data security requirements and the requirements to fix the defects that cause runtime failures or affect the accuracy of data. Important If a major defect occurs in a minor version and the defect causes major losses to users, such as losses due to security issues or data accuracy, the Realtime Compute for Apache Flink team can unpublish the minor version and update the version to a new compatible version. |
EOFS | The Realtime Compute for Apache Flink team no longer develops new patches for the engine version and no longer provides technical support services for the version. | The Realtime Compute for Apache Flink team no longer accepts after-sales technical support requests. The team only provides migration suggestions to users for all requests. |
EOS | Realtime Compute for Apache Flink no longer provides the related services and support for this version. | Users can no longer run existing deployments or create deployments in Realtime Compute for Apache Flink. |
Related services and notifications
Based on the preceding lifecycle policy rules, Alibaba Cloud performs the following operations:
Plan the lifecycle of each service type and engine version of Realtime Compute for Apache Flink and provide information to users during service consultation and the use of service.
Notify users at least four months before the specific time for each milestone by using a notification channel, such as announcements, internal messages, emails, or text messages. Notify users at least three months before the specific time for each milestone of the engine version.
Help users evaluate the risks of running deployments and provide solutions before the service type or engine version service is terminated.
References
For more information about the release notes for Apache Flink engine versions and platform upgrades, see Release notes.
For more information about the enterprise-level state backend storage GeminiStateBackend and the performance comparison between GeminiStateBackend and RocksDBStateBackend, see GeminiStateBackend.
For more information about the version updates or product activities of Realtime Compute for Apache Flink, see Service notices of Realtime Compute for Apache Flink. You can also log on to the Realtime Compute for Apache Flink console to view the version updates or product activities.