Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

Explore the code

Jump to bottom
Miguel Veloso edited this page Jun 22, 2021 · 2 revisions

This page covers the exploration of eShopOnContainers' code base assumes you've already:

  • Setup your development system for Windows or Mac

CONTENT

Overview of the application code

In this repo you can find a sample reference application that will help you to understand how to implement a microservice architecture based application using .NET Core and Docker.

The example business domain or scenario is based on an eShop or eCommerce which is implemented as a multi-container application. Each container is a microservice deployment (like the basket-microservice, catalog-microservice, ordering-microservice and the identity-microservice) which is developed using ASP.NET Core running on .NET Core so they can run either on Linux Containers and Windows Containers. The screenshot below shows the VS Solution structure for those microservices/containers and client apps.

  • (Recommended when getting started) Open eShopOnContainers-ServicesAndWebApps.sln for a solution containing just the server-side projects related to the microservices and web applications.
  • Open eShopOnContainers-MobileApps.sln for a solution containing just the client mobile app projects (Xamarin mobile apps only). It works independently based on mocks, too.
  • Open eShopOnContainers.sln for a solution containing all the projects (All client apps and services).

In the image above you can see:

  1. The src/ApiGateways/Envoy folder, that contains the configuration .yaml file for the Envoy-implemented gateway.

  2. The src/ApiGateways/Mobile.Bff.Shopping and src/ApiGateways/Web.Bff.Shopping folders, with the HTTP aggregators.

  3. The src/BuildingBlocks/EventBus folder, that contains a simplified messaging abstraction, and implementations for RabbitMQ and for Azure Service Bus.

  4. The src/Services/Basket folder, with the Basket microservice. A simple CRUD data-driven microservice that uses Redis for persistence.

  5. The src/Services/Catalog folder, with the Catalog microservice. A simple CRUD data-driven microservice, that uses EF Core and SQL Server.

  6. The src/Services/Identity folder, with the Identity microservice. A Security Token Service (STS), based on Identity Server 4, that also uses SQL Server for persistence.

  7. The src/Services/Ordering folder, that's the home for several microservices:

    • The core Ordering microservice, an advanced Domain Driven Design (DDD) microservice, that uses several DDD patterns and SQL Server for persistence.
    • The Ordering Background Tasks microservice, that uses a BackgroundService for processing asynchronous tasks.
    • The SignalR hub microservice, that works a as centralized hub, based on SignalR, to enable real-time notifications about the order process.

  8. The src/Services/Payment folder, with the Payment microservice, that simulates a simple payment gateway.

  9. The src/Services/WebMVC folder, with the MVC UI microservice, a traditional MVC web application.

  10. The src/Services/WebSPA folder, with the SPA UI microservice, an Angular-based SPA application.

  11. The src/Services/WebStatus folder, with the Web Status microservice, a health monitoring application, based on the open source Xabaril/AspNetCore.DiagnosticsHealthChecks project.

  12. The tests/ServiceTests folder, with some inter-services integration tests.

MVC Application (ASP.NET Core)

It's an MVC application where you can find interesting scenarios on how to consume HTTP-based microservices from C# running in the server side, as it is a typical ASP.NET Core MVC application. Since it is a server-side application, access to other containers/microservices is done within the internal Docker Host network with its internal name resolution.

SPA (Single Page Application)

Providing similar "eShop business functionality" but developed with Angular, Typescript and slightly using ASP.NET Core MVC. This is another approach for client web applications to be used when you want to have a more modern client behavior which is not behaving with the typical browser round-trip on every action but behaving like a Single-Page-Application which is more similar to a desktop app usage experience. The consumption of the HTTP-based microservices is done from TypeScript/JavaScript in the client browser, so the client calls to the microservices come from out of the Docker Host internal network (Like from your network or even from the Internet).

Xamarin Mobile App (For iOS, Android and Windows/UWP)

It's a client mobile app supporting the most common mobile OS platforms (iOS, Android and Windows/UWP). In this case, the consumption of the microservices is done from C# but running on the client devices, so out of the Docker Host internal network (Like from your network or even the Internet).

Additional resources

eShopOnContainers

Getting started

FREQUENT ERRORS

Explore

Deployment

Local

Production (generic)

Cloud

Other Deployment Scenarios

DevOps

Clone this wiki locally