This docker compose file is based on the example of running the Table-Top Infrastructure.
This docker-compose.yml will start the following services:
- Zookeeper: Apache Zookeeper, an internal service, required for managing the state of connected client (what group of clients have read what messages). In case a client crashes, it can continue processing messages where it crashed.
- Broker: Apache Kafka is an open-source distributed event streaming platform used by thousands of companies for high-performance data pipelines, streaming analytics, data integration, and mission-critical applications. All TTI messages are streamed over Kafka between different solutions.
- Schema registry: Each published message must adhere to a an AVRO-based schema, so each connected client knows exactly what information it receives.
- Kafka REST: A REST client for getting information from Kafka.
- Kafka topics UI: An optional service to easily inspect the Kafka topics, and the messages that were sent.
- Kafka schema registry UI: An optional service to easily inspect the AVRO schemas that are used per topic (each topic is associated with one and only one schema, but a schema may have different versions).
- Bootstrapper: A service that runs on startup, registering all required schemas and topics. When creating new schema files, just add them to the
schemasfolder and add their name to thePRODUCE_TOPICSenvironment variable of the bootstrapper, so the producer can create them on start-up. - C2app: A command and control application for First Responders
Go to docker/simulation folder and follow the instructions in the readme.md in that folder.
To start all the services in the background (-d flag) run the following command in the current folder:
docker-compose up -dIf you have nodejs installed, you can try dockly (npm i -g dockly).
Alternatively, if the Docker plugin is installed in VS code, the logs can be shown by right clicking on the running image and pressing "Logs".