APIs and Microservices in ASP.NET Core Today and Tomorrow
summary
Demonstrates concrete features to build microservices: adds health checks (including port-restricted endpoints), integrates Swagger/Swashbuckle plus API conventions and analyzers, and uses HTTPClientFactory as outgoing middleware for retries and circuit breakers. Shows a working console generic host with hosted services, DI, logging and a demo Azure Storage queue worker that invokes methods via a queue handler attribute (it runs and hits breakpoints). Mentions WebJobs SDK reuse, generated clients, and plans for gRPC, metrics and distributed tracing.
AI-written summary · about
chapters (10)
- 0:00Start
- 20:03And that Seems like a Problem Don't You Agree It'Ll Be Nice if When You F5 Didn't Visual Studio It Gave You Something New Something More Useful than a Browser To Browse Your Api that You Don't Really Use Browsers for so Part of that Is Giving You a Swagger Ui Experience Part of that Is We'Re Going To Experiment with a Command-Line Tool To Be Able to Nav once You'Ve Got Swagger We'Ll Give You like a Directory Tree You'Ve Got To Navigate around Your Application You'Ve GotTa Execute Gets You'Ll Be Able To Do a Post
- 28:32It Makes Sense It's this Is Going To Be the Thing That Does Everything Else It's Going To Remove It's Going To Do the Work Do They Get the Stuff from the Queue and Things like that so We'Re GonNa Implement I Hosted Service Right So Yep Use that and Then Controlled Out Again Implement Interface so this Is What the Interface Looks like It's Just Start and Stop with a Cancellation Token so What the Generic Host Gives Us Is It Looks Takes Care of Lifecycle like I Can Control See this Thing Name Properly without Having To Try and Handle Control See and Stuff like that in My Console
- 28:50So this Is What the Interface Looks like It's Just Start and Stop with a Cancellation Token so What the Generic Host Gives Us Is It Looks Takes Care of Lifecycle like I Can Control See this Thing Name Properly without Having To Try and Handle Control See and Stuff like that in My Console Application That's Already Done for You with like a Couple of Lines of Config You Could Switch It Over To Listen to Window Service Events so this Could Become a Window Service for Example or that's Taken Care of You Di Config Logging Is all Built in Now It all Works Exactly the Same Way It Does in Asp Net Core
- 30:08And Then that'Ll Let Us Continue To Control that Which Is the Best Way That I Like To Program Is Just Control Dot until all of My Problems Are Done We Don't Have a Config but this Is Already Saying Go and Grab this Connection String from Config Here Which Is One of the One of the Goals of Our Comments Earlier Right Was To Try and Use Config because that Seems like a Good Idea I'Ve Heard Occasionally You Want To Change Things like Connection Strings So Let's Make a Constructor
- 42:47Extensions
- 49:02Micro-Services Architecture
- 52:40Mqtt
- 53:09Observability
- 55:35End Points and End Point Routing
related talks
51mBuilding Web APIs with ASP.NET Core
48mBuilding Microservices Using ASP.NET Core and AKS
28mMicroservices Made Easy!
59mASP .NET Basics for Experts
01h 00mConsolidating Services With Middleware
01h 04mNavigating microservices with .NET Core
54mBuilding a High-Load-Capable REST API
01h 00mBackground Services in ASP.NET Core and .NET