Galapagos is a DevOps Self-Service Software for Apache Kafka, including an opinionated approach on how to use Kafka for event-driven enterprise architecture.
See Event-Driven Architecture Principles for our principles for an Enterprise-wide Event-Driven Architecture, and Kafka Guidelines for the guidelines for Kafka usage which result directly from these principles. Galapagos is our tool to "enforce" these Guidelines, while not putting additional burden on DevOps teams.
The current Demo Setup sets up two Kafka Clusters and a Keycloak instance in a local Minikube. It uses certificate-based authentication for Kafka.
But we highly recommend to start with the Confluent Cloud based Setup. See Confluent Cloud Setup for details. It only creates a Keycloak instance in a local Minikube; the Kafka clusters are created in a Confluent Cloud subscription. This consumes much less local resources and is much easier to setup. Also, you will get a setup where you can run Galapagos from your IDE, enabling you to start developing on Galapagos and contribute to this great project :-)
Currently, Galapagos supports self-hosted Kafka Clusters which must use Client Certificate-based authentication, as well as Confluent Cloud with their API Key + Secret mechanism. Teams can generate API Keys + secrets for their applications via the Galapagos UI (or via REST).
Discussions are now live! Get in touch - let us talk about the fundamentals, the setup, recommendations for others...
To build Galapagos, just run
mvn package
to get a Spring Boot executable JAR.
To run Galapagos locally for a first test, just use start-galapagos.sh for startup. Please note that you must have
executed one of the devsetup/setup-dev-*.sh scripts first - see Demo Setup above.
In production, you should use one of the Galapagos Docker images available at DockerHub. Recommended is using Kubernetes as execution environment. Configuration can be provided e.g. via ConfigMaps. See Kubernetes Docs for details.