3 ms·

Every request gets it's own process and memory space which tears down after the request is complete. Unless there's leaks in the runtime itself, you're pretty m

Every request gets it's own process and memory space which tears down after the request is complete. Unless there's leaks in the runtime itself, you're pretty much unable to create memory leaks in your application code

digianarchist 6y ago
That's fine for request/response cycles. What about long running background jobs?