Skip to content

Latest commit

 

History

History
135 lines (85 loc) · 10.8 KB

README.md

File metadata and controls

135 lines (85 loc) · 10.8 KB
eShop logo

.NET Microservices Sample Reference Application

Sample .NET Core reference application, powered by Microsoft, based on a simplified microservices architecture and Docker containers.

SPA Application (Angular)

Build Status (GitHub Actions)

Image Status Image Status
Web Status Web Status Shopping Aggregator (Web) Web Shopping Aggregator
Basket API Basket API Shopping Aggregator (Mobile) Mobile Shopping Aggregator
Catalog API Catalog API Web Client (MVC) WebMVC Client
Identity API Identity API Web Client (SPA) WebSPA Client
Ordering API Ordering API Webhooks Client Webhooks demo client
Payment API Payment API Ordering SignalR Ordering SignalR

Dev branch contains the latest beta code and their images are tagged with :linux-dev in our Docker Hub

Getting Started

Make sure you have installed and configured docker in your environment. After that, you can run the below commands from the /src/ directory and get started with the eShopOnContainers immediately.

docker-compose build
docker-compose up

You should be able to browse different components of the application by using the below URLs :

Web Status : http://host.docker.internal:5107/
Web MVC :  http://host.docker.internal:5100/
Web SPA :  http://host.docker.internal:5104/

Blazor WebAssembly web client

This fork adds a Blazor WebAssembly web client, available at:

Web SPA - Blazor : http://host.docker.internal:5106

Or when deployed to local Kubernetes (AOT compiled), at:

Web SPA - Blazor : http://localhost/webblazor

Note: If you are running this application in macOS then use docker.for.mac.localhost as DNS name in .env file and the above URLs instead of host.docker.internal.

Below are the other avenues to setup eShopOnContainers.

Basic scenario

The basic scenario can be run locally using docker-compose, and also deployed to a local Kubernetes cluster. Refer to these Wiki pages to Get Started:

Advanced scenario

The Advanced scenario can be run only in a Kubernetes cluster. Currently, this scenario is the same as a basic scenario with the following differences:

In the future, more features will be implemented in the advanced scenario.

IMPORTANT NOTES!

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 requests 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 main 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

Updated for .NET 7

eShopOnContainers is updated to .NET 7 "wave" of technologies. Not just compilation but also new recommended code in EF Core, ASP.NET Core, and other new related versions with several significant changes.

See more details in the Release notes wiki page.

PLEASE Read our branch guide to know about our branching policy

DISCLAIMER

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.

Architecture overview

This reference application is cross-platform at the server and client-side, thanks to .NET 7 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.

Related documentation and guidance

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 PDF Download PDF

For more free e-Books check out .NET Architecture center. If you have an e-book feedback, let us know by creating a new issue here: https://github.com/dotnet-architecture/ebooks/issues

Are you new to microservices and cloud-native development?

Take a look at the free course Create and deploy a cloud-native ASP.NET Core microservice on MS Learn. This module explains microservices concepts, cloud-native technologies, and reduces the friction in getting started with eShopOnContainers.

Read further

Sending feedback and pull requests

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.