Skip to content
CAI
Software that uses CAICheck a score

mostafasharaby/E-Commerce-Microservices

44.4

Weak · 8 November 2026

6.5k

lines of production code

C#

primary language

4

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

This system is a .NET 8-based microservices platform designed for e-commerce operations, orchestrating the full lifecycle of online shopping. It coordinates distinct services for authentication, product cataloging, inventory management, shopping carts, wishlists, orders, and payments. The architecture leverages shared infrastructure for caching, messaging, and validation to support these interconnected business capabilities.

Features

API Gateway routing and configuration

The ApiGateWay service is introduced, providing a unified entry point for client requests. It uses Ocelot to route traffic to downstream microservices for products, orders, payments, authentication, carts, wishlists, and inventory. The configuration includes rate limiting, caching, JWT authentication, and header injection for each route.

src/ApiGateWay · medium confidence

Add shared infrastructure for authentication, messaging, caching, and error handling

This change introduces a new \SharedService\ library that provides reusable components across the microservices architecture. It adds JWT authentication configuration, a generic repository pattern with unit-of-work support, and a validation behavior for FluentValidation integration. It also includes a RabbitMQ message producer for asynchronous communication, a Redis-based distributed cache service, and a global exception handling middleware that standardizes error responses. Additionally, it provides a generic \Response\<T\>\ wrapper for API results, localization resources for multi-language support, and Swagger configuration for API documentation.

src/SharedService · high confidence

Cart service API and application layer

The CartService now exposes a full REST API for managing shopping carts, including creating, updating, deleting, and retrieving carts by ID or user ID. The implementation uses a MediatR-based command/query pattern with FluentValidation for input validation. The service connects to a SQL Server database and utilizes Redis for caching cart data. Additionally, a background service has been added to consume 'order.failed' events from a message queue to release inventory stock when an order fails.

src/CartService · high confidence

Introduce Auth Service with full user authentication and management capabilities

The Auth Service is introduced, providing a complete authentication and user management system. This includes endpoints for user registration (admin and standard users), login, password management (change, forgot, reset), email confirmation, and account deletion. It supports Google OAuth login and JWT-based authentication with token refresh capabilities. The service also exposes APIs to retrieve user profiles and manage user details, backed by an Entity Framework Core database context and FluentValidation for input validation.

src/AuthService · high confidence

Introduce Payment Service with order integration and background processing

The Payment Service is introduced, providing a new API to create, update, and query payments. The service integrates with the Order Service to validate orders before processing payments. Background services are added to consume 'order.created' events from a message queue, process payments, and publish 'payment.processed' events. The database schema is initialized with a 'Payments' table, and the service is configured with dependency injection, including MediatR, AutoMapper, and FluentValidation.

src/PaymentService · high confidence

Launch of the Inventory Service

The Inventory Service is now available, providing endpoints to manage stock levels. Users can add, reserve, release, update, and reconcile stock quantities, as well as query current stock and identify low-stock items. The service integrates with RabbitMQ to automatically create inventory records when new products are created, and uses a SQL database with Redis caching for performance.

src/InventoryService · high confidence

Launched the Product Service with full CRUD operations and stock integration

The Product Service is now live, exposing endpoints to create, update, delete, and retrieve products, as well as search and check stock levels. The service implements a clean architecture with MediatR handlers, FluentValidation, and AutoMapper. It integrates with an Inventory Service to fetch stock information and uses Redis caching for performance. The default Weather Forecast functionality has been removed.

src/ProductService · high confidence

Order service exposes full CRUD and cart-integration endpoints

The OrderService now provides a complete set of order management capabilities. Users can create, retrieve, update, and delete orders via REST endpoints. The service integrates with external systems: it validates customer and product existence via the AuthService and ProductService, and supports creating orders directly from a user's shopping cart. Additionally, the service is configured with HTTP clients for Inventory, Cart, and Payment services, and includes a Dockerfile for containerized deployment.

src/OrderService · high confidence

Wishlist service API and application layer implementation

The Wishlist service is now fully implemented, exposing a REST API for managing user wishlists. The \WishlistsController\ exposes endpoints to create, read, update, and delete wishlists, as well as add or remove items. The application layer implements the full CRUD and item-management logic using the MediatR pattern, with handlers processing commands and queries. The infrastructure layer provides the \WishlistDbContext\ for database access, a repository pattern for data operations, and a caching strategy using Redis. Additionally, a database migration script and entity mappings are included to support the new schema.

src/WishListService · high confidence

Dependencies

Initial .NET 8 microservices architecture with shared libraries and test scaffolding

The project introduces a new .NET 8 microservices architecture, establishing the foundational structure for services including Auth, Cart, Inventory, Order, Payment, Product, and Wishlist. Each service is organized into a standard layered architecture (Api, Application, Domain, Infrastructure, and Tests) and references a shared library containing common dependencies such as Entity Framework Core 8.0.14, MediatR 12.4.1, and RabbitMQ.Client 6.8.1. The update also adds test scaffolding using xUnit and Moq across all services.

(dependencies) · high 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 44 → 44 (+0.4)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 74 → 74 (+0.0)
  • Architecture 77 → 69 (-7.8)
  • Maturity 49 → 51 (+2.1)
  • Readiness 26 → 26 (+0.0)
  • Security 51 → 53 (+2.8)
  • Domain Modelling 87 → 87 (+0.0)
  • Event-Driven 100 → 100 (+0.0)
  • Performance 100 → 100 (+0.0)

Resolved (35)

  • Cross-context type LowStockDto (InventoryService → ProductService) (src/ProductService/ProductService.Infrastructure/Interfaces/IProductRepository.cs)
  • Cross-context type LowStockDto (InventoryService → ProductService) (src/ProductService/ProductService.Infrastructure/Repositories/ProductRepository.cs)
  • Inconsistent casing and naming conventions for migration classes and methods. 'WishList' uses PascalCase with an internal capital, while 'wishlistInt', 'order_init', 'auth_init', and 'paymentinit' use lowercase or mixed casing with underscores. Additionally, 'wishlistInt' appears to be a truncated or non-standard name compared to the full descriptive names of other migration classes.
  • Inconsistent naming for validation/existence checks. 'ValidateProductExistence' uses 'Existence' while 'ValidateOrderExists' and 'ValidateProductExists' use 'Exists'. Additionally, 'CartExpirationBackgroundService' is a noun phrase describing the service, while 'ValidateOrderExists' is a verb phrase describing an action, but they are both validators/validators-like entities. More critically, 'ValidateProductExistence' vs 'ValidateProductExists' is a direct inconsistency for the same concept (checking if a product exists).
  • Spelling error in 'GetAppointmentConfirmationEamil' (missing 'g' in 'Email'). While 'UpdateWishlist' is correctly spelled, the presence of the typo in the email service method indicates a lack of consistency in spelling accuracy across the codebase.
  • XML-doc coverage: Auth.Api (src/AuthService/Auth.Api/Auth.Api.csproj)
  • XML-doc coverage: Auth.Application (src/AuthService/Auth.Application/Auth.Application.csproj)
  • XML-doc coverage: Auth.Domain (src/AuthService/Auth.Domain/Auth.Domain.csproj)
  • XML-doc coverage: Auth.Infrastructure (src/AuthService/Auth.Infrastructure/Auth.Infrastructure.csproj)
  • XML-doc coverage: CartService.Api (src/CartService/CartService.Api/CartService.Api.csproj)
  • XML-doc coverage: CartService.Application (src/CartService/CartService.Application/CartService.Application.csproj)
  • XML-doc coverage: CartService.Domain (src/CartService/CartService.Domain/CartService.Domain.csproj)
  • XML-doc coverage: CartService.Infrastructure (src/CartService/CartService.Infrastructure/CartService.Infrastructure.csproj)
  • XML-doc coverage: InventoryService.Api (src/InventoryService/InventoryService.Api/InventoryService.Api.csproj)
  • XML-doc coverage: InventoryService.Application (src/InventoryService/InventoryService.Application/InventoryService.Application.csproj)
  • XML-doc coverage: InventoryService.Domain (src/InventoryService/InventoryService.Domain/InventoryService.Domain.csproj)
  • XML-doc coverage: InventoryService.Infrastructure (src/InventoryService/InventoryService.Infrastructure/InventoryService.Infrastructure.csproj)
  • XML-doc coverage: OrderService.Api (src/OrderService/OrderService.Api/OrderService.Api.csproj)
  • XML-doc coverage: OrderService.Application (src/OrderService/OrderService.Application/OrderService.Application.csproj)
  • XML-doc coverage: OrderService.Domain (src/OrderService/OrderService.Domain/OrderService.Domain.csproj)
  • …and 15 more

API surface

  • Unchanged — 57 HTTP endpoints

Architecture

  • Unchanged — 11 containers · 5 contexts · 2 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

mostafasharaby/E-Commerce-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.

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 6550ae120814ab6244074236010cd0169aac4651 — 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.