Tutorials ASP.NET Core Tutorial
Middleware Pipeline — Complete Guide
Middleware Pipeline — Complete Guide: free step-by-step lesson with examples, common mistakes, and interview tips — part of ASP.NET Core Tutorial on Toolliyo Academy.
On this page
ASP.NET Core Tutorial (ShopNest) · Lesson 22 of 100
Middleware Pipeline
Beginner ✓ → Intermediate → Advanced → Professional
Intermediate · 2 — Building apps · ~14 min read · Module 3: Services & Pipeline
Introduction
You know the basics now. Here we use Middleware Pipeline in real app situations — controllers, databases, and APIs. Still plain language, just a bit more depth. Middleware is code that runs on every HTTP request — in order — before and after your controller. Logging, HTTPS redirect, authentication, and routing are all middleware. You add cross-cutting features once instead of copying the same check into every controller action.
The pipeline and DI container are the heart of ASP.NET Core. Every request passes through them before your code runs.
When will you use this?
Reach for middleware and DI when requests need logging, auth, or shared services.
- Middleware handles auth, logging, and errors before your controller runs.
- Dependency injection gives each request its own DbContext without you writing new everywhere.
Real-world: Flipkart-style order service
The E-commerce team building Flipkart-style order service uses Middleware Pipeline to run logging and exception handling on every HTTP request. customers and warehouse staff never see the C# code — they just get a fast, reliable product catalog and checkout API.
Production-style code
var app = builder.Build();
app.UseHttpsRedirection();
app.UseStaticFiles();
app.UseRouting();
app.UseAuthentication();
app.UseAuthorization();
app.MapControllers();
app.Run();What happens in production: In Flipkart-style order service, getting Middleware Pipeline right means customers and warehouse staff trust the product catalog and checkout API every day.
Lesson example (start here)
Copy this smaller example first. Once it works, compare it with the real-world code above.
var app = builder.Build();
app.UseHttpsRedirection();
app.UseStaticFiles();
app.UseRouting();
app.UseAuthentication();
app.UseAuthorization();
app.MapControllers();
app.Run();Line-by-line walkthrough
| Code | What it means |
|---|---|
var app = builder.Build(); | Part of the Middleware Pipeline example — read it together with the lines before and after. |
app.UseHttpsRedirection(); | Middleware or endpoint mapping — part of the request pipeline in Program.cs. |
app.UseStaticFiles(); | Middleware or endpoint mapping — part of the request pipeline in Program.cs. |
app.UseRouting(); | Middleware or endpoint mapping — part of the request pipeline in Program.cs. |
app.UseAuthentication(); | Middleware or endpoint mapping — part of the request pipeline in Program.cs. |
app.UseAuthorization(); | Middleware or endpoint mapping — part of the request pipeline in Program.cs. |
app.MapControllers(); | Middleware or endpoint mapping — part of the request pipeline in Program.cs. |
app.Run(); | Part of the Middleware Pipeline example — read it together with the lines before and after. |
How it works (big picture)
- Order matters.
- Authentication must run before Authorization.
- MapControllers is where routes connect to your actions.
Do this on your computer
- Open Program.cs and read middleware order.
- Add app.Use(async (ctx, next) => { ... await next(); }) to log request path.
- Run and watch the console.
- Read the real-world section and name which part of the app uses this topic.
- Run the example locally with dotnet run and confirm the same behavior.
- Change one value in the example (route, text, or connection string) and predict what will happen before you save.
Experiments — try changing this
- Change a string or route in the example and save — watch the browser or Swagger response update.
- Break the code on purpose (remove a semicolon), read the error message, then fix it.
- Use dotnet watch run while editing Middleware Pipeline — the app restarts on save.
Remember
Each Use* is one middleware piece. Order is critical. Request flows down the pipeline and back.
Common questions
Where does my controller run?
After routing middleware matches the URL to an endpoint.
How long should I spend on Middleware Pipeline?
Until you can explain it in your own words and run the example without looking at the answer. Beginners often need 30–60 minutes per new concept; setup lessons may take one afternoon.
What if I get stuck on Middleware Pipeline?
Re-read the line-by-line walkthrough, check the terminal for red errors, and compare your code character-by-character with the example. Search the exact error text — someone else had it too.
Where is Middleware Pipeline used in real jobs?
See the real-world section above — the same pattern appears in LMS, banking, e-commerce, and SaaS backends. Interviewers ask you to explain it using one concrete example.