The kafka-connect-zeebe Benchmark

OUTDATED/UNMAINTAINED: This project uses Zeebe 0.x, and Zeebe is already on version > 1.0 with some API changes. In order to leverage this project you need to upgrade all components.

This project runs a simple benchmark on https://github.com/zeebe-io/kafka-connect-zeebe to check thorughput for different test scenarios.

cd docker
docker-compose up

I personally run this on a Google Compute Engine (n1-standard-8 (8 vCPUs, 30 GB memory) and then connect via SSH with port forwarding:

ssh -L 9200:localhost:9200 -L 8080:localhost:8080 -L 9021:localhost:9021 -L 8083:localhost:8083 -i ~/gke_key bernd_ruecker_camunda_com@34.89.200.201

Docker compose will start:

Zeebe, on port 26500 for the client, and port 9600 for monitoring.
- To check if your Zeebe instance is ready, you can check http://localhost:9600/ready, which will return a 204 response if ready.
Kafka, on port 9092.
- Zookeeper, on port 2081.
Kafka Connect, on port 8083.
Monitoring tools
- Operate on port 8080.
  - Operate has an external dependency on Elasticsearch, which we'll also run on port 9200.
- Confluent Control Center, on port 9021. This will be our tool to monitor the Kafka cluster, create connectors, visualize Kafka topics, etc.
- Grafana: http://localhost:3000 (admin/admin)

This Docker Compose file is based on the examples provided by Zeebe and Confluent:

zbctl --insecure deploy process.bpmn

This python script does the whole test driving (parameters saying 1 instance with payload type 1):

python run-test.py 1 1

In order to run it you need to install python and:

pip install requests
pip install zeebe-grpc
pip install confluent-kafka
pip install elasticsearch
pip install prometheus_client

The test script

Start workflow instances
Start Kafka Connect Source so that records are written to Kafka, and then stop it again
Start Kafka Connect Sink so that records are correlated back to Zeebe
Wait for all workflows to be completly finished

It will print the durations of the different tasks.