Sign in or create an account for a best experience.
5 | Sign In | 6 | Create Account 7 |4 | The Account microservice 5 | manages account information. It persists its data primarily on 6 | a MySQL container and process operations such as creating accounts, 7 | changing password, granting access to the system (no JWT so far), etc. 8 |
9 |4 | The Order microservice 5 | manages order information and workflow. It persists its data primarily on 6 | a MySQL container and communicates to the other microservices primarily 7 | via asynchronous messages exchanged via a RabbitMQ container. 8 |
9 |4 | The Newsletter microservice 5 | manages newsletter information. It persists email subscriptions primarily on 6 | a MySQL container. There's no default implementation for newsletter 7 | oprations such as a scheduled job, etc. Feel free to implement yours. 8 |
9 |4 | The Payment microservice 5 | simulates a payment gateway and manages the payment workflow. 6 | It persists its data primarily on a MySQL container and communicates 7 | to the other microservices primarily via asynchronous messages exchanges 8 | via a RabbitMQ container. 9 |
10 |These are the last events for your account.
8 |These are the existing orders for your account.
8 |4 | The Web microservice 5 | is this ASP.NET app that you're accessing at the moment. 6 | It's essentially a BFF (backend for frontend) / Api Gateway 7 | and is the public interface between the user and the other 8 | microservices. Web caches catalog, recommendation and data 9 | from other services on a Redis container. 10 |
11 |Here's your account info.
8 | 9 |Here's your list of payment types.
8 | 9 |13 | Already have an account? Sign In 14 |
15 | 16 |Here's your list of addresses.
10 | 11 |4 | The Recommendation microservice 5 | simulates a recommendation service by implementing naive recommendations 6 | based on previously completed shopping carts. 7 | It persists its data primarily on a MySQL container and communicates 8 | to the other microservices primarily via asynchronous messages exchanges 9 | via a RabbitMQ container. 10 |
11 |Welcome back, @name!
10 || Event | 7 |Date | 8 |
|---|---|
| {{ h.info }} | 13 |{{ new Date(h.createdAt).toDateString() }} | 14 |
You have no unread notifications.
10 |
4 | The catalog is provided by the
5 | Catalog microservice
6 | which consists of an ASP.NET Core app pulling data from a
7 | MongoDB container. The catalog is initialized with the
8 | docker-compose script. To change the catalog
9 | information, check th db.js file on the
10 | CatalogSvc project.
11 | The catalog information is cached locally
12 | from the Web microservice on a Redis container.
13 |
4 | Notifications are provided via asynchronous messages 5 | exchanged via a RabbitMQ Docker container and processed by a .NET Core backend. 6 | Different events (such as newsletter signups, account registrations, etc) 7 | send an async message to the 8 | Notification microservice 9 | that's sends and email to the user using Gmail by default. 10 | The notification service also logs the history of sent messages on a 11 | dedicated MySQL database. 12 |
13 |4 | The Shipping microservice 5 | simulates a shipping service and is reached via a RabbitMQ queue 6 | and MassTransit. The service is triggered by the order workflow 7 | whenever shopping carts are approved from the fake 8 | Payment microservice. 9 | The service persists its data primarily on a MySQL container and communicates 10 | to the other microservices primarily via asynchronous messages exchanges 11 | via a RabbitMQ container. 12 |
13 |@(Model.Description ?? $"Here's our list of products under {Model.Name}")
10 |
5 | This is a sample application to demo Microservices in .NET
6 | using ASP.NET Core, Docker, Redis, MongoDB, MySQL, Vue.js, MassTransit,
7 | Azure and Kubernetes.
8 | The source code is
9 | MIT licensed
10 | and is available at
11 | github.com/hd9/aspnet-microservices.
12 |
Check our selection of {{ c.name }}.
14 | View all products in {{ c.name }} 15 |22 | Don't have an account? Create Account. 23 |
24 |
12 | Request ID: @Model.RequestId
13 |
18 | Swapping to Development environment will display more detailed information about the error that occurred. 19 |
20 |21 | The Development environment shouldn't be enabled for deployed applications. 22 | It can result in displaying sensitive information from exceptions to end users. 23 | For local debugging, enable the Development environment by setting the ASPNETCORE_ENVIRONMENT environment variable to Development 24 | and restarting the app. 25 |
26 | -------------------------------------------------------------------------------- /src/Microservices.Core/Microservices.Core.csproj: -------------------------------------------------------------------------------- 1 |Please review the information below. You'll have a chance to review your cart on the next step.
8 |Congratulations, your order was submitted. Here's the summary of your order:
11 |Sorry but the order you requested could not be found.
16 |Sorry, no recommendations found yet for this product.
18 |
5 | Want to subscribe to our newsletter?
6 | List managed by our Newsletter Microservice.
7 |
Help and information about the project.
5 | 6 |This project is composed of the following microservices:
9 |7 |
35 |