Consolidating Services With Middleware
summary
Argues that HTTP microservices benefit from reusable middleware and shows concrete code: builds a timing middleware, a correlation ID middleware that reads or emits a header and wires it into logging and outgoing HTTP clients, and a monitor endpoint short-circuiting middleware that returns version/health. Uses ASP.NET Core pipeline (Kestrel) plus class-vs-lambda patterns, packages middleware as NuGet, and demonstrates interoperability with LibOwin/OWIN. Explains how these components make logging, monitoring and auth uniform and easily testable across many services.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:12Why Middleware
- 2:34Microservice Systems
- 3:02Why Microservices
- 6:46Examples
- 15:10Microservices
- 19:27Web Server
- 20:35Pipes and Filters
- 24:28Pipelines
- 27:19Pipeline Example
- 31:10Empty Web Application
- 31:38Running Empty Web Application
- 32:57Creating Middleware
- 41:02Reusing Middleware
- 42:02Logging Contexts
- 46:43Monitoring Endpoints
- 49:40Sharing Across Libraries
related talks
01h 05mAPIs and Microservices in ASP.NET Core Today and Tomorrow
52mLightweight microservice collaboration using HTTP
57mUnderstanding Microservices: a guide for the monolithic developer
54m12 Factor MicroServices
46mFrom Monolithic Monster to Majestic Microservice App
43mGo micro with Microservices
01h 04mNavigating microservices with .NET Core
10mMicroservices, Messaging, and Failure: How Simplifying Our Architecture Saved Us
