Hazelcast is releasing Hazelcast Platform 5.7, introducing a variety of updates aimed at data resilience.
Central to the launch is Advanced CP, a premium add-on to Hazlecast's already strongly consistent Raft-based side of the platform, specifically built to support multi-data-center topographies, the company said.
New features include:
Advanced CP: predictable strong consistency in stretched deployments
Platform 5.7 introduces Advanced CP; a premium add-on built specifically for multi-data-center topologies:
- CP Auto Leader Step Down. Automatically transfers Raft leadership away from high-latency or quorum-only sites, so every CP write is bounded by the fastest quorum path rather than the slowest part of the topology.
- CP Smart Client Routing. Clients route CP reads and writes directly to the relevant Raft leader, removing relay hops and stabilizing latency through leadership changes.
- CP Map. A strongly consistent, linearizable key-value store for the small but critical control-plane state that sits between transactions and the ledger.
A few things Advanced CP is not: it is not a new consensus protocol (Raft is unchanged), not a way to escape quorum latency, and not a general-purpose cache. It is a control layer for stretched, regulated deployments where leadership drifting into the wrong failure domain has historically meant manual intervention.
Baseline CP capabilities—production-grade CP data structures, persistence, rolling upgrades, observability—remain part of the base Platform subscription. Advanced CP is the upgrade for topologies where manual recovery is not an acceptable answer.
Continuous operations: infrastructure change without downtime
Platform 5.7 closes out the operational hardening of the stream processing engine (formerly Jet), and Hazelcast Platform Operator 5.18 raises the floor on what “running in Kubernetes” means for a tier-1 workload.
Stream processing hardening
- Lossless recovery from full cluster restart
- Live job upgrades with no downtime
- Namespace isolation so multiple business pipelines coexist cleanly on one cluster
- Job placement control for more predictable execution
Operator 5.18
- Automatic TLS certificate rotation without cluster restart
- Faster pod recovery (no unnecessary JAR re-downloads)
- GitOps-friendly logging through ConfigMap
- ModuleDeploy support for Management Center classpath extension
- Cleaner separation of pod failure behavior from initialization noise
For architects, this is real-time pipelines that survive change. For platform engineering, it’s fewer scheduled outages, less drift between environments, and GitOps-native operations. For the board and the regulator, continuous operation becomes a configuration rather than a heroic effort.
Evidence-ready observability
Management Center 5.11 and the GA of Dynamic Diagnostic Logging materially expand what operators can see—and prove—about platform behavior.
The shift in 5.7 is that observability is now organized around the questions risk committees and auditors actually ask—leadership behavior, state consistency, change windows, evidence of control—rather than just metrics and dashboards.
Performance and modernization without forced migration
Performance gains that require a refactor are rarely deployed at the institutions that need them most. Platform 5.7 delivers drop-in upgrades across the client surface area.
- .NET client 5.7.0.
- Coming soon: C++ client
- Java 25 support across Platform, Management Center, and Operator.
- Python AsyncIO support for modern asynchronous codebases, including the AI and inference pipelines increasingly sitting alongside core enterprise systems.
Vector Collections advance to Release Candidate
Vector Collections move to RC1 in this release, with split-brain protection, a maturing public API, and Operator support.
Hazelcast Platform 5.7 ships as both an Open Source and an Enterprise release. OSS remains a strong path for development, experimentation, and team building with Hazelcast.
When Hazelcast becomes part of a production operating model, including support expectations, patch obligations, upgrade windows, Kubernetes operations, observability requirements, and resilience evidence, the conversation naturally shifts to Enterprise. Future 5.7.x patches will be Enterprise-only, making this a natural moment for OSS users running Hazelcast in production to revisit where their roadmap falls on that line.
For more information about this news, visit https://hazelcast.com.