Infrastructure prerequisites
Before proceeding with the setup, ensure that the following components have been set up:- Redis - version 6.0 or higher
- Kafka - version 2.8 or higher
Dependencies
- Kafka - used for event communication
- Redis - used for caching
Configuration
Configuring Kafka
Set the following Kafka-related configurations using environment variables:SPRING_KAFKA_BOOTSTRAP_SERVERS- the address of the Kafka server, it should be in the format “host:port”
Groupd IDs
The configuration parameters “KAFKA_CONSUMER_GROUP_ID_*” are used to set the consumer group name for Kafka consumers that consume messages from topics. Consumer groups in Kafka allow for parallel message processing by distributing the workload among multiple consumer instances. By configuring the consumer group ID, you can specify the logical grouping of consumers that work together to process messages from the same topic, enabling scalable and fault-tolerant message consumption in your Kafka application.Threads
The configuration parameters “KAFKA_CONSUMER_THREADS_*” are utilized to specify the number of threads assigned to Kafka consumers for processing messages from topics. These parameters allow you to fine-tune the concurrency and parallelism of your Kafka consumer application, enabling efficient and scalable message consumption from Kafka topics.Kafka topics related to process instances
Kafka topics related to tasks
Configuring authorization & access roles
Set the following environment variables to connect to the identity management platform:Redis
The process engine sends the messages to the events-gateway, which is responsible for sending them to Redis.Master replica
The events-gateway can be configured to communicate with Redis using the MASTER_REPLICA replication mode by configuring the following property:spring.data.redis.sentinel.nodes: replica1, replica2, replica3, etc…
Correspondent environment variable:
SPRING_DATA_REDIS_SENTINEL_NODES
Example
By default, Redis is standalone, so the configuration with
redis-replicas is optional for high load use cases.spring.redis.sentinel.nodes property is used to specify the list of Redis Sentinel nodes that the Spring application should connect to. These nodes are responsible for monitoring and managing Redis instances.