Skip to content
CAI
Software that uses CAICheck a score

thangchung/coffeeshop-on-dapr

46.6

Weak · 8 November 2026

4.4k

lines of production code

C#

primary language

7

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Features

Add Bicep and Dapr/KEDA configuration files for Azure infrastructure and service scaling

The iac directory now includes a complete set of Bicep templates to define the Azure infrastructure (AKS, Container Registry, Service Bus) and application services (Postgres, reverse proxy, and each microservice). Additionally, Dapr component YAMLs are provided for both Azure (Service Bus) and local (Redis) environments, and KEDA ScaledObject definitions are added to enable automatic scaling of the barista, counter, and kitchen services based on Azure Service Bus message counts.

iac · high confidence

Initial project scaffolding with .NET 7 and MediatR pipeline behaviors

The repository is initialized with a new .NET 7-based architecture. This includes a DataGen background worker service that generates test data by posting random orders to a CoffeeShop API, and a shared core library (N8T.Core) providing domain entities, domain events, and a specification pattern for query composition. The infrastructure layer (N8T.Infrastructure.EfCore) introduces Entity Framework Core with Npgsql/PostgreSQL support, including a transactional MediatR pipeline behavior (TxBehavior) that wraps requests in database transactions and publishes domain events. The setup also includes repository abstractions, helper classes, and configuration options.

(repo-wide) · high confidence

Initial release of the .NET coffeeshop application on Dapr

The repository is initialized with the full source code for a .NET 7-based microservices application, including services for product, counter, barista, and kitchen operations, along with a reverse proxy. The release includes Docker Compose configurations for local development with Dapr sidecars, an observability stack (OpenTelemetry, Prometheus, Jaeger, Zipkin), and infrastructure-as-code templates (Bicep) for deploying to Azure Kubernetes Service. A Makefile and client.http file are provided to simplify building, pushing images, and testing the APIs.

(repo-wide) · high confidence

Introduce Product Service with item catalog and query endpoints

The Product Service is now available, providing endpoints to retrieve the full list of available items and to fetch specific items by their types. Users can access the item catalog via GET /v1/api/item-types and query items by type via GET /v1/api/items-by-types/{itemTypes}. The service is configured to run on port 5001 and includes a Dockerfile for containerization.

src/ProductService · high confidence

Behavioural changes

Added development container and domain contracts for Dapr integration

Developers can now use the new .devcontainer configuration to run the project in a consistent environment with Nomad, Consul, and CNI plugins pre-installed. Additionally, new C\# contracts (BaristaOrderUpdated, BaristaOrdered, KitchenOrderUpdated, KitchenOrdered, ItemDto, ItemType, and ItemTypeDto) were added to the CoffeeShop.Contracts library, supporting the shift to a Dapr-based architecture.

.devcontainer, src/Libs/CoffeeShop.Contracts · medium confidence

Introduce Dapr-based event publishing for order and kitchen events

The Barista and Counter services now use Dapr to publish domain events to message buses. The Barista service publishes \BaristaOrderUp\ events to the \orderuppubsub\ topic, while the Counter service publishes \BaristaOrderIn\ and \KitchenOrderIn\ events to the \baristapubsub\ and \kitchenpubsub\ topics respectively. This replaces the previous direct or internal event handling with a distributed pub/sub model.

src/BaristaService, src/CounterService, src/KitchenService · high confidence

Dependencies

Initial project setup with .NET 7 and core libraries

The project is initialized with .NET 7.0 as the target framework across multiple services (Barista, Counter, Kitchen, Product) and libraries (N8T.Core, N8T.Infrastructure, etc.). Key dependencies include Entity Framework Core 7.0, MassTransit 8.0.8, OpenTelemetry 1.4.0-beta.3, and Yarp.ReverseProxy 1.1.1, establishing the foundational architecture for the application.

(dependencies) · medium confidence

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

How this codebase got here

Score

  • CAI 43 → 47 (+3.1)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 70 → 70 (+0.2)
  • Architecture 83 → 83 (+0.1)
  • Maturity 62 → 68 (+5.9)
  • Readiness 24 → 29 (+5.3)
  • Security 50 → 50 (+0.0)
  • Domain Modelling 66 → 66 (+0.0)
  • Event-Driven 100 → 100 (+0.0)
  • Performance 100 → 100 (+0.0)

Resolved (19)

  • Confusing naming and potential overlap: ItemDto contains Price and Type, while ItemTypeDto contains Type and Name. It is unclear if 'Type' in ItemDto refers to the same entity as 'Type' in ItemTypeDto. If ItemTypeDto is the canonical definition of an item type, ItemDto should likely reference it by ID or name, not duplicate the 'Type' field which might be ambiguous. Furthermore, having two 'Dto' types for what seems to be a single concept (Item details) is confusing.
  • Coverage not measured — no coverage collector is wired up
  • Documentation: no contributor guidance (README.md)
  • Duplicate intent: BaristaOrderUpdated and KitchenOrderUpdated are structurally identical (OrderId, ItemLineId, Name, ItemType, TimeIn, MadeBy, TimeUp). Like the 'Ordered' types, these represent the same state change for different consumers.
  • Duplicate intent: BaristaOrdered and KitchenOrdered are structurally identical (OrderId, ItemLineId, ItemType). They likely represent the same domain event or data transfer object for different consumers, but maintaining two separate types with identical shapes creates redundancy and synchronization overhead.
  • End-of-life runtime: .NET net7.0 (src/ReverseProxy/ReverseProxy.csproj)
  • Inconsistent naming for configuration property accessors. One property uses a verb phrase 'GetConnectionString' while the other uses a simple noun phrase 'Password'. In a configuration options class, properties should consistently be named as nouns (e.g., ConnectionString, Password) rather than mixing verbs and nouns.
  • Vulnerable: OpenTelemetry.Instrumentation.AspNetCore
  • Vulnerable: OpenTelemetry.Instrumentation.Http
  • Vulnerable: Yarp.ReverseProxy
  • XML-doc coverage: BaristaService (src/BaristaService/BaristaService.csproj)
  • XML-doc coverage: CoffeeShop.Contracts (src/Libs/CoffeeShop.Contracts/CoffeeShop.Contracts.csproj)
  • XML-doc coverage: CounterService (src/CounterService/CounterService.csproj)
  • XML-doc coverage: DataGen (src/DataGen/DataGen.csproj)
  • XML-doc coverage: KitchenService (src/KitchenService/KitchenService.csproj)
  • XML-doc coverage: N8T.Core (src/Libs/N8T.Core/N8T.Core.csproj)
  • XML-doc coverage: N8T.Infrastructure (src/Libs/N8T.Infrastructure/N8T.Infrastructure.csproj)
  • XML-doc coverage: N8T.Infrastructure.EfCore (src/Libs/N8T.Infrastructure.EfCore/N8T.Infrastructure.EfCore.csproj)
  • XML-doc coverage: ProductService (src/ProductService/ProductService.csproj)

New (11)

  • Duplicated block (64 lines × 3) (src/BaristaService/Program.cs)
  • End-of-life runtime: .NET net7.0 (src/BaristaService/BaristaService.csproj)
  • End-of-life runtime: .NET net7.0 (src/CounterService/CounterService.csproj)
  • End-of-life runtime: .NET net7.0 (src/DataGen/DataGen.csproj)
  • End-of-life runtime: .NET net7.0 (src/KitchenService/KitchenService.csproj)
  • End-of-life runtime: .NET net7.0 (src/Libs/CoffeeShop.Contracts/CoffeeShop.Contracts.csproj)
  • End-of-life runtime: .NET net7.0 (src/Libs/N8T.Core/N8T.Core.csproj)
  • End-of-life runtime: .NET net7.0 (src/Libs/N8T.Infrastructure.EfCore/N8T.Infrastructure.EfCore.csproj)
  • End-of-life runtime: .NET net7.0 (src/Libs/N8T.Infrastructure/N8T.Infrastructure.csproj)
  • End-of-life runtime: .NET net7.0 (src/ProductService/ProductService.csproj)
  • End-of-life runtime: .NET net7.0 (src/ReverseProxy/ReverseProxy.csproj)

API surface

  • Unchanged — 10 HTTP endpoints

Architecture

  • Unchanged — 9 containers · 4 contexts · 3 edges

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

Survey your own repository

thangchung/coffeeshop-on-dapr 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.

About this page

  • The score is its most recent published measurement, taken on 8 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit ad04bfae172c731bc26500694dfbbfd935595606 — the exact code this score is about.
  • Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
  • Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-45ab2cab63de.