Apache Kafka - Features

To take full advantage of Apache Kafka as a Distributed System, cegedim.cloud ensures that brokers are dispatched on multiple Availability Zones to maximize resiliency and redundancy.


The default cluster sizing includes 3 brokers provisionned over 3 Availability Zones.

The default configuration also ensure that the replication factor is set to 3 for topics and the minimum in-sync replica has to be 2.

This configuration garantees that all your topics and messages are replicated on all brokers over all the Availability Zones.

Note that provisioning more than 3 brokers will complexify things.

The more brokers, the more you will replicate your data. If you don't want to replicate more than 3 times, you will have to micro manage which topics and partitions are replicated and where in order to comply with your DRP for example.

High level diagram


The provided Apache Kafka cluster is secured by the following means :

  • Inter broker communications secured with SASL_SSL

  • Client to broker communications secured with SASL_SSL

  • Secure controllers with ACLs

Controllers are managed by cegedim.cloud, simplifying your administration.

To connect to your secure Kafka cluster the following will be required :

  • The corresponding certificate

  • An existing and authorized user with a password (SCRAM-SHA-256)

Please refer to Apache Kafka - Get started to connect and interact with your Kafka cluster.

Default configuration

Important Apache Kafka broker parameters kept at default:



The number of hours to keep a log file before deleting it.


The maximum size of the log before deleting it : no limits.

1073741824 (1 gibyte)

The maximum size of a single log file.

300000 (5 minutes)

The frequency in milliseconds that the log cleaner checks whether any log is eligible for deletion.

Custom configuration

Here are the kafka broker parameters that cegedim.cloud will modify during provisioning:




Enable auto creation of topic on the server.



Default number of log partitions per topic. More partitions allow greater parallelism for consumption, but will also result in more files across the brokers.Replication factor is equal to the number of brokers participating in the cluster. (3 to 5)



Le facteur de réplication est égal au nombre de brokers participant au cluster. (3 à 5)



The minimum number of replicas that must acknowledge a write for the write to be considered successful for a producer that sets acks to "all" (or "-1").



Equals to the number of CPUs of the virtual machine.



Number of fetcher threads used to replicate messages from a source broker. Increasing this can increase the degree of I/O parallelism in the follower broker.

Last updated