.NET Core Microservices - The Complete Guide (.NET 8 MVC)

Learn Microservices architecture with .NET Core MVC(.NET 8), Entity Framework Core, .NET Identity with Azure Service Bus

4.52 (7261 reviews)

Udemy

platform

English

language

Other

What you will learn

.NET Core Microservices - The Complete Guide (.NET 8 MVC)

Implementing 7 microservices using .NET 8

.NET API with Authentication and Authorization

Role based authorization with .NET Identity

Async and Sync communication between Microservices

Azure Service Bus - Topics and Queues

Gateways in Microservices

Implementing Ocelot gateway

Swagger Open API implementation

N-Layer implementation with Repository Pattern

ASPNET Core Web Application with Bootstrap 5

Entity Framework Core with SQL Server Database

Charts

Students

Price

Rating & Reviews

Enrollment Distribution

Comidoc Review

Our Verdict

This .NET Core Microservices course offers in-depth knowledge and practical experience with microservices, API design, and service integration. While there are areas for improvement, such as updating outdated content and addressing interdependent databases, the course's strengths lie in its hands-on approach, clear explanations, and coverage of essential concepts. Recommended for those looking to learn about microservices in .NET Core.

What We Liked

Comprehensive coverage of .NET Core Microservices, including 7 individual microservices and N-Layer implementation with Repository Pattern.
Hands-on approach to understanding essential concepts like independent service design, API Gateway setup, and managing communications between services using Azure Service Bus.
Clear explanations and structured approach from the instructor, making complex concepts easier to understand and apply in real-world projects.
Valuable introduction to Stripe for implementing online payments.

Potential Drawbacks

Interdependent nature of microservices' databases, which conflicts with the core principle of microservices architecture.
Lack of Kubernetes usage for service management and deployment, which could enhance stability, scalability, and independence of each service.
Some sections, particularly those on Azure and RabbitMQ, are considered outdated and may require updates or re-recording.
Minor issues like visible passwords during login/registration and the use of non-descriptive variable names detract from the overall quality.