How is the processing of multiple simultaneous requests handled within a single-process Scoped context?

In a single-process context with Scoped lifetime dependencies in ASP.NET Core, each HTTP request receives its own instance of services with a Scoped lifetime. When multiple requests are executed simultaneously within the same process, a separate Scoped container is created for each request, isolated from others.

This is achieved through the use of the DI container mechanism, which creates a new scope at the beginning of a request and disposes of it at the end. Thus, even in a single-process application, each request operates with its own set of Scoped services, preventing data conflicts between requests.

Here's an example:

// In Startup.cs
services.AddScoped<IMyService, MyService>();

// A new scope is created for each request
app.Use(async (context, next) => {
    using (var scope = app.ApplicationServices.CreateScope())
    {
        var myService = scope.ServiceProvider.GetRequiredService<IMyService>();
        // Use myService within the request
        await next();
    }
});

In reality, ASP.NET Core automatically creates a scope for each HTTP request, so developers usually do not need to create it manually.