Sample .NET Core reference application, powered by Microsoft, based on a simplified microservices architecture and Docker containers.
| Image | Status | Image | Status |
|---|---|---|---|
| Api Gateway (base) | Shopping Aggregator (Web) | ||
| Basket API | Shopping Aggregator (Mobile) | ||
| Catalog API | Web Client (MVC) | ||
| Identity API | Web Client (SPA) | ||
| Location API | Web Status (Health) | ||
| Marketing API | Webhooks API | ||
| Ordering API | Webhooks Client | ||
| Payment API |
Dev branch contains the latest beta code and their images are tagged with :dev in our Docker Hub
eShopOnContainers is provided in two flavors: Basic and Advanced.
Basic scenario cab be run locally using docker compose, and also deployed to a local Kubernetes cluster. Refer these Wiki to Get Started:
- Using Visual Studio
- Using CLI or Visual Studio Code
- Using docker compose
- Using local Kubernetes
The Advanced scenario can be run only in a Kubernetes cluster. Currently this scenario is the same as basic scenario with the following differences:
- Use of a Service Mesh for Resiliency
In the future more features will be implemented in the advanced scenario.
You can use either the latest version of Visual Studio or simply Docker CLI and .NET CLI for Windows, Mac and Linux.
Note for Pull Requests (PRs): We accept pull request from the community. When doing it, please do it onto the DEV branch which is the consolidated work-in-progress branch. Do not request it onto master branch.
NEWS / ANNOUNCEMENTS Do you want to be up-to-date on .NET Architecture guidance and reference apps like eShopOnContainers? --> Subscribe by "WATCHING" this new GitHub repo: https://github.com/dotnet-architecture/News
eShopOnContainers is updated to .NET Core 3.0 "wave" of technologies. Not just compilation but also new recommended code in EF Core, ASP.NET Core, and other new related versions.
-
Migrate solution from ASP.NET Core 2.2 to 3.0 and update all projects to use the latest .NET Core 3.0 templates.
-
Implement the new .NET Core 3.0 WorkerService in Ordering.API and other background processes.
-
Improve Ordering.API
- Group order items
- apply discounts from Marketing.API
-
Handle two deployment scenarios
-
Basic deployment, better for learning:
- Docker compose
- Local Kubernetes
- Visual Studio F5 experience
-
Advanced deployment, complex but more real-life:
- Sidecar implementation with Envoy/Linkerd
- Improved API Gateway and resilience
- gRPC for inter-service communications
- Test and Support Azure Dev Spaces
-
The repo also has a new, simpler, folder structure, as shown in the following image:
In the above image you can see that the first folder level contains, basically:
- build: Scripts for building Docker images.
- deploy: Scripts for deployment.
- src: All source projects, including tests.
- ApiGateways: Envoy configuration and Aggregators source code.
- BuildBlocks: Common components used by several projects.
- Mobile: Mobile apps projects.
- Services: Backend for all services. Including unit and functional tests for some projects.
- Basket
- Catalog
- Identity
- Location
- Marketing
- Ordering
- Payment
- Webhooks
- Tests: General functional application tests.
- test-results: Test results
- Web: Web applications
PLEASE Read our branch guide to know about our branching policy
IMPORTANT: The current state of this sample application is BETA, because we are constantly evolving towards newly released technologies. Therefore, many areas could be improved and change significantly while refactoring the current code and implementing new features. Feedback with improvements and pull requests from the community will be highly appreciated and accepted.
This reference application is cross-platform at the server and client side, thanks to .NET Core services capable of running on Linux or Windows containers depending on your Docker host, and to Xamarin for mobile apps running on Android, iOS or Windows/UWP plus any browser for the client web apps. The architecture proposes a microservice oriented architecture implementation with multiple autonomous microservices (each one owning its own data/db) and implementing different approaches within each microservice (simple CRUD vs. DDD/CQRS patterns) using Http as the communication protocol between the client apps and the microservices and supports asynchronous communication for data updates propagation across multiple services based on Integration Events and an Event Bus (a light message broker, to choose between RabbitMQ or Azure Service Bus, underneath) plus other features defined at the roadmap.
You can find the related reference Guide/eBook focusing on architecting and developing containerized and microservice based .NET Applications (download link available below) which explains in detail how to develop this kind of architectural style (microservices, Docker containers, Domain-Driven Design for certain microservices) plus other simpler architectural styles, like monolithic apps that can also live as Docker containers.
There are also additional eBooks focusing on Containers/Docker lifecycle (DevOps, CI/CD, etc.) with Microsoft Tools, already published plus an additional eBook focusing on Enterprise Apps Patterns with Xamarin.Forms. You can download them and start reviewing these Guides/eBooks here:
| Architecting & Developing | Containers Lifecycle & CI/CD | App patterns with Xamarin.Forms |
|---|---|---|
 |
 |
 |
| Download .PDF | Download | Download |
Download in other formats (eReaders like MOBI, EPUB) and other eBooks at the .NET Architecture center.
If you've an eBook feedback, create a new issue here: https://github.com/dotnet-architecture/ebooks/issues
However, we encourage you to download and review the Architecting and Developing Microservices eBook because the architectural styles and architectural patterns and technologies explained in the guide are using this reference application when explaining many pattern implementations, so you'll understand the context, design and decisions taken in the current architecture and internal designs much better.
Read the planned Roadmap within the Wiki for further info about possible new implementations and provide feedback at the ISSUES section if you'd like to see any specific scenario implemented or improved. Also, feel free to discuss on any current issue.