Overview
The startup sequence timeline shows the exact order of service registration in the API host: from the initial WebApplicationBuilder, through Aspire service defaults, core runtime registration, persistence adapter setup, multi-scheme authentication, API pipeline configuration, schema initialization, middleware mapping, and finally health-check readiness.
Key takeaways
- Core Runtime registers first — clock, user context, audit, tenant resolver, and authorization
- Persistence Adapters are switchable via
Persistence:Providerconfig (SqlSugar or EF Core) - API Pipeline registers Mediator with 7 pipeline behaviors plus Mapster and rate limiting
- Schema initialization (
--init-schema) runs before the web pipeline starts
Related
- Request Lifecycle — what happens after startup
- DI Tree — service registration hierarchy