Differences between terminal middleware vs non-terminal middleware Type Description Terminal Ends the pipeline. Doesn’t call next(). E.g., app.Run() Non-Termi nal Calls next() and allows other middlewares to run after it. E.g., app.Use() Terminal middleware:

Short answer: pp.Run(async ctx => { wait ctx.Response.WriteAsync("This ends the pipeline"); }); pp.Run(async ctx => { wait ctx.Response.WriteAsync("This ends the pipeline"); }); pp.Run(async ctx => { wait ctx.Response.WriteAsync("This ends the pipeline"); }); pp.Run(async ctx => { wait ctx.Response.WriteAsync("This ends the pipeline"); });

Real-world example (ShopNest)

ShopNest pipeline order matters: exception handling → HTTPS → auth → authorization → endpoints. Auth must run before protected APIs.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.