Reversibility Policy for the Managed Message Broker product

Objective

This document describes the reversibility policy of the Managed Message Broker product covering the OVHcloud Managed Kafka offer.

This policy aims to implement the general reversibility principles and our compliance with the SWIPO IAAS Code of Conduct for cloud providers.

List of features

The features of the Managed Document Database product line fall into three categories:

Core features for which we guarantee migration capacity.
OVHcloud implementations that require adaptation to a new migration environment.
Specific features that cannot be guaranteed for migration as they are related to the OVHcloud environment or involve custom developments.

1 - Core features

Function	Description	Available formats	Migration model	Available documentation
High-availability message streaming	Reliable and distributed transmission of real-time data.	Avro, JSON, Protocol, Text	Incoming: Loading via Kafka producers . Outgoing: Export via Kafka consumers or replay tools.	Kafka - Capabilities and limitations
Open-source Kafka compatibility	Use the standard Apache Kafka engine without modification.	Native Kafka (standard API)	Incoming: Direct integration with existing Kafka tools. Outgoing: Standard Kafka export	Kafka getting started documentation
Partitioning and replication	Manage partitions and replicas for fault tolerance	N/A	Incoming: Configure partitions/replicas on import. Outbound: Export and deploy to another cluster.	Kafka - Capabilities and limitations
Configuring data retention	Custom message retention duration setting	NA	Incoming: Adjusting parameters. Outgoing: Migration limited to messages that are still stored.	Kafka - Advanced settings references
Data Schema Registry	Central repository for storing data schemas	Karapace Native Format	Inbound: NA. Outbound: NA.	Schema registry

2 - OVHcloud implementations

Function	Description	Available formats	Migration model	Available documentation
OVHcloud Dashboard	Manage topics, ACLs and monitor via web interface.	N/A	Incoming: Initial configuration via API and web interface. Outbound: Administration interrupted after termination. Reproduce configurations manually in target environment	Dashboards - Capabilities and limitations Dashboards - Advanced settings references
Integrated monitoring	Performance dashboards integrated into the OVHcloud interface.	N/A	Inbound: Metrics Configuration. Outbound: Configuration to recreate in the target environment.	Analytics - Kafka
Network Security (ACL)	IP filtering and SSL/SASL authentication.	IP, SASL/SSL	Incoming: Rule configuration. Outbound: Export ACLs to replicate.	Kafka - Getting started

3 - Specific features

Function	Description	Available formats	Migration model	Available documentation
OVHcloud private network (vRack)	Connect to other OVHcloud services via a private network.	N/A	Incoming: vRack configuration. Outgoing: Non-transferable feature.	vRack
Anti-DDoS	Anti-DDoS is a set of tools and mechanisms designed to absorb denial of service attacks. It includes traffic analysis, "clean-up" via a specialized network, and mitigation using VAC technology developed by OVHcloud.	N/A	Incoming: The anti-DDoS system is part of our infrastructure and is enabled by default. No action is required. Outgoing: Order and configure an anti-DDoS solution from the new provider.	OVHcloud DDoS Protection

List of architectures

The Managed Kafka service is based on a distributed architecture with Kafka brokers distributed across several availability zones. High availability is ensured via partition replication, with integrated monitoring for message flow stability. Two architecture plans are offered: a Business plan based on three nodes and an Enterprise plan based on six nodes.

Partner Services

The OVHcloud partners concerned are listed in the OVHcloud partners directory under the "cloud migration" keywords.

OVHcloud also has a dedicated service: OVHcloud Professional Services.

Costs and fees

The features described in the tables are available at no cost, unless otherwise specified, and are freely usable by the customer. The service is billed according to the resources used: the selected instance and the storage. No cancellation fee will be applied, but you will need to export the data before cancelling/decommissioning the service.

Data retention after termination of contract

After the service has been cancelled, all Kafka messages and configurations are permanently deleted. The customer must perform a full export before termination, as OVHcloud does not store any data.

Was this page helpful?