Tutorials on ASP.NET Core, Blazor, jQuery, JavaScript, Entity Framework, Identity, WordPress, SQL, HTML & more

Microservices API Gateway to unify Multiple Microservices

In a Microservices Architecture, clients often need to call many different service URLs, which quickly becomes hard to manage. An API gateway such as Ocelot solves this by acting as a single entry point: it receives each incoming HTTP request from the client and forwards it to the appropriate microservice. Ocelot is configured through a JSON file that defines the upstream and downstream routes.

An upstream request is the request the client sends to the API gateway, while a downstream request is the request the gateway sends on to the Microservice.

You can find the complete Source Code at my GitHub Repository.

ASP.NET Core Microservices Synchronous Communication

In the previous tutorial, we built the first ASP.NET Core Microservice for our drone pizza delivery application, called CommandCenter. In this tutorial, we will build the second Microservice, called ProcessCenter. This Microservice will handle the delivery of pizza orders by drones and will communicate synchronously with the first Microservice. A MongoDB database will store all of the microservice’s records.

First ASP.NET Core Microservice with Web API CRUD Operations on a MongoDB Database

This tutorial walks through creating a first Microservice in ASP.NET Core that handles CRUD operations against a MongoDB database via Web API endpoints. The service will serve as one component of a drone pizza delivery application.

A Practical Guide to API Versioning in ASP.NET Core – Complete Guide

API versioning is the practice of managing changes to an API over time by labeling different iterations of it, so that existing consumers (apps, scripts, other services) aren't broken when the API evolves.

In practice, it means: instead of having one single, ever-changing version of your API, you maintain distinct, identifiable versions — like v1 and v2 — so that:

• Old clients can keep calling the version they were built against.
• New clients (or updated old ones) can call the newer version with new features/fields/behavior.
• Both can coexist during a transition period.

OpenAPI Support in ASP.NET Core Web API Apps: A Complete Guide

OpenAPI is a standard specification for describing HTTP APIs in a machine-readable format. In an ASP.NET Core Web API application, OpenAPI can describe your API endpoints, HTTP methods, parameters, request and response models, authentication requirements, and other API metadata.

This description can then be used by tools such as Swagger UI to generate interactive API documentation, allowing developers to explore and test API endpoints directly from a web browser.

ASP.NET Core Interview Questions and Answers – Crack Your Next Interview

Cracking an ASP.NET Core interview is not just about memorizing a list of interview questions—it is about understanding how the framework works and being able to apply that knowledge to real-world development scenarios. Interviewers often test your understanding of core concepts such as Dependency Injection, middleware, routing, Web APIs, Entity Framework Core, authentication and authorization, performance optimization, and asynchronous programming, along with your ability to solve practical problems. In this guide, we will cover the most important ASP.NET Core interview questions and answers, from beginner-level fundamentals to advanced and scenario-based questions, so you can build confidence and prepare effectively for your next ASP.NET Core interview.

Effortless ASP.NET Core Minimal API Testing with the Visual Studio HTTP Editor

The Visual Studio HTTP File Editor is a powerful built-in tool for testing ASP.NET Core Web APIs and Minimal APIs directly from the IDE. Instead of relying on external tools like Postman, you can create, edit, and execute HTTP requests using .http files, making API development and debugging faster and more efficient.

With the Visual Studio 2026 HTTP File Editor, you can:

• Create and manage .http files for organizing and storing API requests.
• Send HTTP requests (GET, POST, PUT, DELETE, PATCH, and more) directly from Visual Studio.
• View and inspect HTTP responses, including status codes, headers, and response bodies, without leaving the editor.

How to use JSON Patch in ASP.NET Core Minimal API

JSON Patch is a standardized format for describing changes to a JSON document. It is defined by RFC 6902 and is commonly used with HTTP PATCH requests to update resources without sending the entire document.

How to perform Unit and Integration Testing in Minimal APIs

Testing is an essential part of developing ASP.NET Core Minimal APIs because it ensures that API endpoints behave correctly, reliably, and securely. Unit testing verifies the business logic of individual components, while integration testing confirms that endpoints, routing, middleware, dependency injection, and database interactions work together as expected. Regular testing helps identify bugs early, improves code quality, simplifies maintenance, and provides confidence when making changes or adding new features. As a result, testing contributes to building robust, scalable, and maintainable Minimal API applications.

Filters in ASP.NET Core Minimal API

Filters in ASP.NET Core Minimal APIs are components that execute before and/or after a route handler. They allow you to add common functionality such as validation, logging, authentication checks, or modifying requests and responses without repeating code in every endpoint.