What is microservices-clean-architecture?

This repository is a template for building an e-commerce platform using a microservices approach. Instead of one large application, the system is split into several smaller, independent services: ordering, inventory, payments, and fulfillment. A gateway acts as the front door, routing requests from client applications to the correct service. The creator built it as a reference for how to structure distributed systems in a production setting. Each service follows a layered design where dependencies point inward. The innermost layer holds the core business logic and has zero external dependencies. Surrounding layers handle application logic, infrastructure concerns like database access, and the API endpoints. This structure is enforced at compile time, meaning a developer cannot accidentally break the rules. The services communicate in two ways. For immediate needs, they use synchronous gRPC calls, such as reserving stock during order placement. For background processing, they send asynchronous events through a message queue. The payments service handles a saga pattern, which means if a payment fails, the system automatically rolls back or compensates for earlier steps, like releasing reserved stock. The template includes several infrastructure choices. It uses PostgreSQL for writes and Valkey, a Redis alternative, for fast reads. Keycloak handles identity and authentication. YARP serves as the reverse proxy gateway with rate limiting. A tool called Aspire orchestrates the local development environment, providing a dashboard with traces, metrics, and logs. It also ships with independent CI/CD pipelines, allowing each service to deploy on its own schedule. Developers install it as a NuGet template and generate a new project with a few commands. The README includes quick start instructions for running everything locally. The full README is longer than what was shown.