aledeulo/cqrs-examples-customers-and-orders

This system is a microservices-based application for managing customers and orders, built on the Eventuate Tram platform with Spring Boot. It features a multi-module architecture supporting multiple database backends and message brokers, with automated CI/CD pipelines for AWS Fargate deployment. The codebase includes comprehensive end-to-end, migration, and snapshot tests to verify service behavior and data integrity.

This change introduces a complete infrastructure-as-code template for deploying the application on AWS Fargate. It includes Terraform configurations for the ECS cluster, load balancers, and individual service task definitions for the CDC, customer, order, and order-history services. Additionally, it adds AWS CodePipeline and CodeBuild configurations to automate the build and deployment of Docker images to Amazon ECR, along with supporting scripts for database initialization and API invocation.

(repo-wide) · high confidence

The repository is initialized with essential project files, including an Apache 2.0 license, a Gradle wrapper for build automation, and a Layerfile for containerized development environments. To support the microservices architecture, the commit adds Docker Compose configurations for MySQL, PostgreSQL, and MSSQL backends, along with Kafka and Zookeeper services. Additionally, shell scripts are introduced to manage the full test suite across different database backends, and helper scripts are added for interacting with Kafka, MongoDB, and SQL databases.

(repo-wide) · high confidence

New test suites have been added to verify the behavior of the Orders and Customers services. The end-to-end tests validate customer and order creation, approval/rejection logic, and order cancellation. The migration tests verify that message IDs are correctly migrated in the database. The snapshot tests ensure that customer and order snapshots are correctly exported and searchable via the text search service. Configuration files for these tests have also been added.

end-to-end-tests, migration-tests, snapshot-tests · high confidence

The project is initialized with a multi-module Gradle and Maven structure, defining modules for customer and order services, their APIs, and supporting components. Dependencies are configured using the Eventuate Tram platform BOM (version 2021.3.RELEASE) and Spring Boot 2.2.6.RELEASE, with specific libraries like MySQL and PostgreSQL JDBC drivers, Spring Retry, and JMeter for load testing.

(dependencies) · medium confidence

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

• CAI 46 → 47 (+0.9)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 100 → 100 (+0.0)
• Architecture 100 → 93 (-7.2)
• Maturity 52 → 52 (+0.0)
• Readiness 32 → 36 (+3.5)
• Security 41 → 41 (+0.0)
• Domain Modelling 87 → 82 (-4.9)

• Coverage not included — suite not readable by the collector
• Critical IaC: AWS-0104 (aws-fargate-terraform/sg.tf)
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• High IaC: AWS-0030 (aws-fargate-terraform/codepipeline.tf)
• High IaC: AWS-0031 (aws-fargate-terraform/codepipeline.tf)
• High IaC: KSV-0014 (deployment/kubernetes/ingress/local-nginx-ingress.yaml)
• High IaC: KSV-0014 (deployment/kubernetes/ingress/nginx-ingress.yaml)
• High IaC: KSV-0056 (deployment/kubernetes/ingress/local-nginx-ingress.yaml)
• High IaC: KSV-0056 (deployment/kubernetes/ingress/nginx-ingress.yaml)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• Medium: security finding (details withheld)
• Medium: security finding (details withheld)
• No exposed public API
• Scanner failed to run — not a clean result
• Test reliability not included
• early-stage repository — too few commits for a meaningful bus factor
• early-stage repository — too little history to judge knowledge freshness
• git history depth insufficient
• …and 1 more

• Critical IaC: AWS-0104 (aws-fargate-terraform/sg.tf)
• Critical IaC: AWS-0104 (aws-fargate-terraform/sg.tf)
• Critical IaC: AWS-0104 (aws-fargate-terraform/sg.tf)
• Critical IaC: AWS-0104 (aws-fargate-terraform/sg.tf)
• Critical IaC: AWS-0104 (aws-fargate-terraform/sg.tf)
• Dependency hygiene PARTLY measured — Maven/Gradle declarations read, no dependency graph resolved
• Documentation: no licence statement (README.md)
• High IaC: AWS-0030 (aws-fargate-terraform/codepipeline.tf)
• High IaC: AWS-0030 (aws-fargate-terraform/codepipeline.tf)
• High IaC: AWS-0030 (aws-fargate-terraform/codepipeline.tf)
• High IaC: AWS-0031 (aws-fargate-terraform/codepipeline.tf)
• High IaC: AWS-0031 (aws-fargate-terraform/codepipeline.tf)
• High IaC: AWS-0031 (aws-fargate-terraform/codepipeline.tf)
• High IaC: AWS-0164 (aws-fargate-terraform/network.tf)
• High IaC: AWS-0164 (aws-fargate-terraform/network.tf)
• High IaC: AZU-0029 (deployment/terraform_azure/azure_sql.tf)
• High IaC: DS-0002 (java-development/Dockerfile)
• High IaC: DS-0002 (jmeter-service/Dockerfile)
• High IaC: DS-0029 (java-development/Dockerfile)
• High IaC: DS-0029 (jmeter-service/Dockerfile)
• …and 480 more

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

aledeulo/cqrs-examples-customers-and-orders 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.