How tructran91/litecommerce works
Project type and purpose
• This is a .NET-based, learning‐focused e-commerce system built with a microservice architecture.
• It consists of:
• A Blazor SPA (“LiteCommerce.Admin”) as the frontend
• An Ocelot API Gateway
• A set of backend microservices (Catalog implemented; User, Inventory, Order, Payment, Shipping, Notification, Promotion planned)
• A shared library for cross‐cutting concerns
File structure
• Top-level:
• ApiGateways/Ocelot.ApiGateway → API Gateway
• Services/Catalog → the Catalog microservice, further broken down into:
– Catalog.API (ASP.NET controllers, middleware, DI extensions)
– Catalog.Application (CQRS/MediatR behaviors, commands/queries, handlers, validators, services)
– Catalog.Core (domain entities, enums, exceptions, repository interfaces)
– Catalog.Infrastructure (EF Core DbContext, migrations, repository implementations, data seed)
• Shared/LiteCommerce.Shared → shared constants, models, logging
• Web/LiteCommerce.Admin → Blazor client (pages, components, API clients)
• Notice the layered pattern inside each service and the separation of concerns between layers.
README for additional insights
• Confirms microservice goals: modularity, scalability, maintainability.
• Technology stack: .NET 8, SQL Server per service, REST APIs + (future) message broker.
Detail
• Drill down only on implemented flow (Blazor → Gateway → Catalog → CatalogDb).
• Shared components (Shared library) that span multiple services.