GloboTicket is a sample ASP.NET Core Microservices application that you can learn about in the Pluralsight .NET Microservices Learning path. This path consists of the following courses:
- Microservices: The Big Picture
- Getting Started with ASP.NET Core Microservices
- Microservices Communication in ASP.NET Core
- Implementing a data management strategy for an ASP.NET Core Microservices Architecture
- Securing Microservices in ASP.NET Core
- Versioning and Evolving Microservices in ASP.NET Core
- Deploying ASP.NET Core microservices using Kubernetes and AKS
- Implementing cross-cutting concerns for ASP.NET Core microservices
- Strategies for Microservice Scalability and Availability in ASP.NET Core
This repo contains many branches. Each branch corresponds to on eof the demos given in the course. To enable you to follow allong the demos yourself, you can switch to a specific branch for each of the demos. The following demo corresponds to the following branch:
Demo 1, Module 2 -> branch before_containarized_docker_compose Demo 2, module 2 -> branch containarized_docker_compose
Demo 2, Module 3 -> Branch create_acr_and_push Demo 3, Module 3 -> Branch create_acr_and_push Demo 4, Module 3 -> Branch zero_downtime_with_probes
Demo 1, Module 4 -> Branch containarized_allup Demo 2, Module 4 -> Branch containarized_allup
Demo 1, Module 5 -> Branch zero_downtime_dbchange Demo 2, Module 5 -> Branch zero_downtime_dbchange
In order to build and run the sample GloboTicket application, it is recommended that you have the following installed.
- .NET Core 3.1 SDK. You can test that you have it installed by entering the command
dotnet --list-sdks - Entity Framework Command Line Tools. You can install these as a global tool with the command
dotnet tool install --global dotnet-ef - SQL Server Express.
- Visual Studio 2019 (Community Edition or Greater) or Visual Studio Code
You can either load GloboTicket\GloboTicket.sln in Visual Studio 2019 and build from within Visual Studio, or from the command line, in the same folder as GloboTicket.sln, enter the dotnet build command.
Before you run GloboTicket for the first time, you need to run the database migrations for all microservices that have a SQL database. These are the event catalog microservice, and the shopping basket microservice.
First, navigate into the GloboTicket\GloboTicket.Services.EventCatalog folder and run the dotnet ef database update command.
Then, navigate into the \GloboTicket\GloboTicket.Services.ShoppingBasket folder and run the dotnet ef database update command.
You can run the GloboTicket application directly from within Visual Studio. To do this, first right click on each of the three projects individually and view the project properties. In the Debug tab for each of the three projects, ensure that the Launch setting is set to Project (and not IIS Express). This will ensure that each microservice runs on the expected ports.
Then right-click on the solution file and select Set Startup Projects, and configure all three projects to either Start or Start without Debugging as desired. Now, when you run the project from within Visual Studio, all three projects will start up.
Alternatively, you can run the GloboTicket application from the command line. You will need to open three separate command prompts, one for each csproj file. For each project, navigate into the folder containing the .csproj file and run the command dotnet run.
Note: You may be asked to trust the .NET Core developer certificates. Make sure you do so, in order to use HTTPS to access the services.
If you have followed the instructions, the GloboTicket client application (website) will be running on port 5000, which you can access in the browser at https://localhost:5000.
The Event Catalog microservice will be running on port 5001 and you can view the API documentation at https://localhost:5001/swagger
The Shopping Basket microservice will be running on port 5002 and you can view the API documentation at https://localhost:5002/swagger