Production-ready APIs with .NET 7
Having an API ready for production should mean more than just deploying functionality. There are certain architectural aspects that get overlooked, and we think about them when it is too late in the development lifecycle (if we think at all).
In this workshop we will design an API with respect to several non-functional requirements that I consider to be mandatory for anything serious running in production. For this, we will use .NET 7 and we will learn what we can tweak to aid the development process.
Course Structure & Contents
Designing HTTP Apis
- Http methods
- Http status codes
- Http headers
- Endpoint naming
- Media-type selection, design & custom media types
- Caching & Conditional caching
- Input & Output formatters
- Why API design matters
Designing for change
- storing secrets in development and production
- Configuration options & custom configuration providers
- Versioning strategies for backwards and forward compatibility
- Open Telemetry
- Structured Logging
- Monitoring with Jaeger
Performance, Optimization and Scalability
- Load balancing
- Measuring performance
- Compression and caching types
Microsoft MVP for Developer Technologies, Software Architect and Microsoft Certified Trainer, always in a quest for latest trends and best practices in architecture, .NET and the world around it.
Irina has more than 1000 hours of delivered trainings, workshops, and presentations, being passionate about .NET and the world around it.
She is the founder of DotNet Iasi User Group where she tries to gather people that are willing to share their knowledge with others, and from time to time publishes articles on her blog: http://irina.codes