This topic compares the features and benefits of Realtime Compute for Apache Flink with those of the open source version.
Feature | Description | Benefit |
Full compatibility | Ensures complete compatibility with the open source version, including support for APIs across various abstraction levels, parameter configurations, and SQL syntax. | Compared with the open source version, Realtime Compute for Apache Flink provides enhanced performance and fine-grained resource management to help reduce your total cost of ownership (TCO). You can select a billing method based on your business requirements and use automatic scaling to optimize resource utilization. |
Enhanced performance |
| |
Efficient resource utilization | Supports dynamic scaling based on your business requirements. For more information, see Dynamically update the parameter configuration for dynamic scaling. | |
Supports automatic tuning. The system monitors and adjusts deployment resource allocation and executes a resource plan at a specific point in time. This helps ensure stability during peak hours and maintains costs at a reasonable level. For more information, see Configure automatic tuning. | ||
Supports fine-grained resource management. You can configure CPU and memory resources at the operator level for SQL deployments. The resource utilization of large-scale deployments are improved by up to 100%. For more information, see Configure resources for a deployment. | ||
Flexible billing methods | Supports subscription, pay-as-you-go, and hybrid billing. For more information, see Billable items. Billable items. | |
Real-time data ingestion | Supports real-time synchronization of data and schema changes in databases, including those that use sharding or partitioning. For more information, see Data synchronization templates. | You can ingest data from databases or message-oriented middleware into data lakes or data warehouses in real time. |
Real-time fraud detection | Supports enterprise-class complex event processing (CEP). You can dynamically configure rules for a deployment without the need to restart the deployment, which ensures the continuous operational capability in scenarios such as online real-time fraud detection. For more information, see CEP statements. | You can enhance development efficiency and large-scale data processing while ensuring business continuity for mission-critical scenarios, such as real-time marketing, real-time fraud detection, and Threat Detection Service (TDS). |
Various connectors | Built-in connectors:
Custom connectors:
| Realtime Compute for Apache Flink is integrated with various upstream and downstream systems, eliminating the need to build from scratch and ensures system stability and optimal performance. |
Development | Provides an end-to-end development and management platform. You can use SQL, Java, Scala, and Python for development. | You do not need to build from scratch or customize the version provided by Apache Flink. Flink SQL is easy to use and simplifies development. |
Supports mainstream Apache Flink versions. Supports the comparison of different versions of SQL scripts and rollback to a previous version. For more information, see Manage deployment versions. | ||
Supports centralized metadata management. You can use catalogs to connect common upstream and downstream systems, such as MySQL, Apache Hive, Hologres, Data Lake Formation (DLF), and Apache Kafka. For more information, see Manage catalogs. | ||
Supports user-defined functions (UDFs). You can easily manage and use UDFs. For more information, see Manage UDFs. | ||
Provides more than 20 Flink SQL templates for common scenarios to help you quickly get started. For more information, see Code templates. | ||
Debugging | Supports test data management. You can sample online data or generate simulated data to build testing workflows. For more information, see Debug a deployment. | Programmers and data analysts can easily debug and run a deployment. This significantly reduces costs and improves efficiency during the testing stage. |
Supports efficient debugging. You can start or cancel deployments in session clusters within seconds. | ||
Supports display of intermediate results, which improves the efficiency of debugging complex SQL statements. | ||
Supports isolation of the development and production environments. This ensures that debugging operations do not affect deployments and data in the production environment. | ||
Monitoring and alerting | Provides various metrics and aggregation dimensions to help you detect performance issues, such as deployment latency, data skew, and backpressure. For more information, see Metrics. | You can achieve higher system stability with reduced O&M workload, simpler tuning operations, and significantly lower costs. You can also obtain high availability assurance provided by Alibaba Cloud. |
Sends alerts at the earliest opportunity to DingTalk or by email, text message, or call. You can also use Managed Service for Prometheus to receive alerts. For more information, see Report metrics of Realtime Compute for Apache Flink to other platforms. | ||
Issue analysis and diagnostics | Supports dynamic deployment configuration. For example, you can change the log level and enable or disable the flame graph feature without the need to cancel or restart the deployment. | |
Provides intelligent diagnostics for common issues, such as backpressure, deployment errors, and TaskManager disconnections. Issues are identified based on log analysis, and tuning and modification suggestions are automatically generated. For more information, see Perform intelligent deployment diagnostics. | ||
High availability | Guarantees a 99.9% service availability as indicated in the Service Level Agreement (SLA). | |
Supports end-to-end automatic fault recovery, including fault tolerance for JobManagers. This prevents single points of failure and improves service stability. | ||
Supports fast single-node fault recovery to balance data consistency and service continuity. | ||
Supports cross-zone high availability. If faults occur in the primary zone of a cross-zone namespace, jobs will fail over to the secondary zone within the same region. This helps prevent business from being disrrupted by single-zone failures and ensures job continuity and high availability. | ||
State management | Supports complete lifecycle management of system checkpoints and savepoints, state compatibility checks, and state data migration. This ensures maximum reuse of state data. | |
Resource isolation | Provides tenant-level and project-level resource and code isolation. This ensures data security during cross-team collaboration. | Enterprises can perform secure and controlled interdepartmental collaboration based on internal and external audit standards. |
Access control |
| |
Variable management | Supports using variables in deployment development, log export configuration, and UI-based parameter setups. This helps prevent security risks associated with plaintext AccessKey pairs or credentials. |