thecodemonkey/kafka-microservices

This system is a collection of example applications demonstrating Apache Kafka integration using Java and Kotlin. It provides concrete implementations for producing and consuming messages, processing streams, and implementing event sourcing patterns. The repository also includes unit test examples for verifying Kafka interactions without requiring a live cluster.

The hello-kafka-unit-test directory now includes two complete, runnable examples for testing Kafka-based applications: a Java implementation using Maven and a Kotlin implementation using Gradle. Each example demonstrates how to write unit tests for Kafka producers and consumers using EmbeddedKafka and Testcontainers, allowing developers to verify message publishing and consumption without a live Kafka cluster. The changes include all necessary build scripts, wrapper files, and documentation to run the tests via \mvn test\ or \gradle test\.

hello-kafka-unit-test · high confidence

The repository now includes a complete Kafka messaging example implemented in both Java and Kotlin. The Java implementation provides an \App\ entry point, a \Consumer\ that listens to 'hello-topic', and a \Producer\ that sends scheduled messages. The Kotlin implementation mirrors this structure with equivalent \App\, \Consumer\, and \Producer\ classes. Additionally, unit tests have been added for both languages, utilizing Testcontainers and Spring's \EmbeddedKafka\ to verify message publishing and consumption.

(repo-wide) · high confidence

The Hello Kafka API example now includes a Java implementation alongside the existing Kotlin one. This change adds the Java project structure, including Maven wrapper scripts and configuration files (.mvn/), a .gitignore for Java IDEs, and a Java-specific readme. It also moves the Kotlin example's Gradle wrapper and gitignore files to the new hello-kafka-api/kotlin directory, consolidating the API examples.

hello-kafka-api · high confidence

Introduced new Kotlin-based microservices for order management: the order-command-service now produces simulated order events to a Kafka topic, while the order-query-service consumes these events via Kafka Streams to maintain a current-state view of orders, exposing them through a REST API.

hello-kafka-es-streamsapi/kotlin/order-command-service, hello-kafka-es-streamsapi/kotlin/order-query-service · high confidence

The Hello Kafka Streams example is now provided in two separate implementations: a Java version using Maven and a Kotlin version using Gradle. Each variant includes its own build scripts (mvnw/gradlew), configuration, and source code, allowing users to choose their preferred language and build tool.

hello-kafka-streams · high confidence

A new Kotlin-based example for Event Sourcing using Kafka Streams, Spring, and Gradle has been added to the \hello-kafka-es-streamsapi/kotlin\ directory. This includes the project's Gradle wrapper configuration, build scripts, and a detailed README explaining how to run the command and query services via Docker and Gradle to demonstrate event sourcing with Kafka.

hello-kafka-es-streamsapi · high confidence

The project's build system was reorganized to separate Java and Kotlin implementations for Kafka demos. New Maven (pom.xml) and Gradle (build.gradle.kts) configuration files were added for the 'hello-kafka-api', 'hello-kafka-streams', and 'hello-kafka-unit-test' modules. The existing 'hello-kafka' and 'hello-kafka-streams' Gradle projects were renamed and restructured to include both Java and Kotlin source directories, with dependencies for Spring Boot, Spring Kafka, and Testcontainers explicitly defined in the new build scripts.

(dependencies) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 54 → 57 (+2.7)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 100 → 100 (-0.2)
• Architecture 100 → 100 (+0.0)
• Maturity 62 → 65 (+2.8)
• Readiness 25 → 30 (+5.4)
• Security 100 → 96 (-4.1)

• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• LLM evaluation failed
• No exposed public API
• Scanner failed to run — not a clean result
• Test reliability not included
• early-stage repository — too little history to judge knowledge freshness
• git history depth insufficient
• git history depth insufficient
• single-maintainer — knowledge-concentration (bus factor) risk

• Dependency hygiene PARTLY measured — Maven/Gradle declarations read, no dependency graph resolved
• Documentation: no installation or build instructions (README.md)
• Documentation: no installation or build instructions (hello-kafka-api/readme.md)
• Duplicated block (10 lines × 2) (hello-kafka-es-streamsapi/kotlin/order-command-service/src/main/kotlin/kafka/es/command/Producer.kt)
• High IaC: WD-COMPOSE-0001 (docker-compose.yml)
• Medium IaC: WD-COMPOSE-0002 (docker-compose.yml)
• Medium IaC: WD-COMPOSE-0002 (docker-compose.yml)
• Medium IaC: WD-COMPOSE-0002 (docker-compose.yml)
• Medium IaC: WD-COMPOSE-0002 (docker-compose.yml)
• Medium IaC: WD-COMPOSE-0002 (hello-kafka/docker-compose-withui.yml)
• Medium IaC: WD-COMPOSE-0002 (hello-kafka/docker-compose-withui.yml)
• Medium IaC: WD-COMPOSE-0002 (hello-kafka/docker-compose-withui.yml)
• Medium IaC: WD-COMPOSE-0002 (hello-kafka/docker-compose.yml)
• Medium IaC: WD-COMPOSE-0002 (hello-kafka/docker-compose.yml)
• No ADRs found
• Scanner failed to run — not a clean result
• Scanner failed to run — not a clean result

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

thecodemonkey/kafka-microservices was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.