Compatibility
Compatibility belongs to a specific combination of releases. A technology appearing in the ecosystem overview does not mean every version, data type or connector direction is supported.
Managing an existing Flink runtime and using commercial runtime enhancements may have different requirements. Confirm which path applies to your deployment and whether any component must change.
Prepare a component inventory
| Component | Record for the evaluation |
|---|---|
| Realfuture | Product release, licensed components and deployment topology |
| Flink | Exact version, distribution, JDK, workload API and state backend |
| Flink CDC | Version, SQL connector or Pipeline API, and required features |
| Sources and targets | Product and version, read/write direction, authentication and networking |
| Connectors | Artifact versions, dependencies, formats and required data types |
| Infrastructure | Kubernetes or YARN version, deployment mode, storage and resource limits |
| Platform services | Platform database, identity integration, monitoring and backup requirements |
Ask for the release-specific compatibility list before making a production decision. Do not infer support for a combination from separate claims that each individual component is supported.
For CDC pipelines
Use representative tables to check:
- Initial snapshot and transition to incremental changes.
- Data types, primary keys, time zones and update/delete behavior.
- The DDL changes you need and the target system’s response.
- Restart, catch-up and recovery after source, target or network failures.
- Data correctness and delivery semantics for the complete source-to-target path.
Schema evolution and delivery guarantees depend on the connector and configuration. A successful test for one pair does not certify another pair.
For platform integration
Confirm API coverage and authentication, role permissions, monitoring export and the ownership of any additional integration work. Distinguish packaged product behavior from an external integration or a separately scoped engineering service.
Continue with the evaluation guide or migration guide.