This topic describes the product lifecycle policy (PLP) for Realtime Compute for Apache Flink and the runtime lifecycle policy (RLP) for the engine version of Realtime Compute for Apache Flink.

Background information

Product updates and phase-outs are common laws. Due to the growth of the Apache Flink community, services that are deployed on top of Apache Flink are continuously updated to provide more powerful and easier-to-use features. Various business forms, such as engine reconstruction, billing and metering, and cloud-native deployment, are emerging. As a result, the features that are provided by existing versions and service types may fail to meet the increasing business requirements of users. Old products face challenges in terms of application stability, resource elasticity and processing performance, access security, and API compatibility. Therefore, old products are gradually replaced by new products.

Product lifecycle management helps introduce new products and new engine versions based on business requirements. This helps improve user technologies, enhances the efficiency of cloud computing for users, and allows cloud computing vendors to focus on services and prevent ineffective maintenance workloads.

To meet business requirements, such as data migration, verification of the internal cost and stability of a new version, and long-term IT planning, and to provide users with enterprise-level services and strengthen their insights into the future evolution of products, Realtime Compute for Apache Flink provides a lifecycle management system and defines PLP for Realtime Compute for Apache Flink and RLP for the engine version of Realtime Compute for Apache Flink.

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 the delivery, to the end of marketing, and finally to the end of service. 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 time period 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 the PLP of Realtime Compute for Apache Flink.

Key milestonesKey milestones

Definitions of key milestones

Milestone Full name Definition Description
EOM End of Marketing End of marketing New orders including the orders for new purchases and scaling are not accepted. EOM consists of the following stages:
  • EOM1: Orders for new purchases are not accepted.
  • EOM2: Orders for new purchases and scaling are not accepted.
Note The entire EOM phase cannot be less than four months.
EOFS End of Full Support End of full support New versions including patch versions are not released.
Note In the EOFS phase, services, such as answering questions, resolving issues, and handling service level agreement (SLA) guarantee compensation, are no longer provided.
EOS End of Service End of service All support services for the product are not provided.

Limits on each stage of the product delisting process

Milestone Alibaba Cloud public cloud
Announcement to EOM New purchases and renewals are allowed.
EOM to EOFS
  • New purchases are not allowed.
  • Renewals are allowed.
  • Unsubscription is allowed.
  • Configuration upgrade or downgrade is allowed.
  • Temporary updates are allowed.
  • Configuration upgrade or downgrade during renewal is allowed. Users can modify configurations during renewal.
  • Only a configuration modification that is performed before the EOFS phase is allowed.
EOFS to EOS
  • New purchases and renewals are not allowed.
  • Configuration upgrade or downgrade is not allowed.
  • Unsubscription is allowed.
EOS The product is delisted.

Description of RLP

Realtime Compute for Apache Flink uses the enhanced engine Ververica Runtime (VVR). For more information about the engine version planning and meaning, 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 end of marketing, and finally to the end of service.

The time period 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 the RLP of Realtime Compute for Apache Flink.

Key milestonesKey milestones

Definitions of key milestones

Milestone Full name Definition Time Description
GA General Availability Official delivery On the T day The new version can be officially released and delivered to users for use in the production environment.
EOGS End of General Support End of basic support At least 180 days after the T day 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.
EOFS End of Full Support End of full support At least 90 days after the day of EOGS 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 End of Service&Support End of service and support At least 90 days after the day of EOFS Realtime Compute for Apache Flink no longer provides the related services and support for this version. Users cannot run existing jobs or create jobs in Realtime Compute for Apache Flink.
Note
  • The start time of each phase cannot be earlier than the specified time. The specific time for each milestone is notified to users by using a notification channel at least three months in advance. For more information, see Related services and notifications.
  • 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.

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 the information to users during service consultation and the use of service.
  • Notify users of the key milestones in the product lifecycle by using announcements, in-site letters, emails, or text messages at least four months before the arrival of the key milestones. For the key milestones of the engine version, Alibaba Cloud notifies users at least three months before the arrival of the key milestones.
  • Help users evaluate the risks of running jobs and discuss solutions before the service type or engine version service is terminated.

Alibaba Cloud expects that users can participate in product and engine version lifecycle management. Users can inform Alibaba Cloud of any questions, suggestions, or expectations about product and engine version lifecycle management. Users can provide feedback during service consultation or in user service groups, and can also submit a ticket or contact sales representatives.

Alibaba Cloud aims to meet the real-time business requirements of enterprises and cloud product development based on effective communication to provide users with efficient and stable cloud services.