liveBook · Manning

Process manager

As explained in ASP.NET Core in Action, 3e

A process manager is software that monitors application processes and can restart or supervise them when they fail.

A process manager monitors an application process and restarts it when it crashes or stops responding. This keeps the application available for handling requests. section 27.3.1

In Linux deployments, a reverse proxy forwards incoming requests, while a separate process manager such as systemd supervises the application. This separation matters because the reverse proxy may run on another server and cannot restart the application. IIS combines both responsibilities on Windows; Docker deployments commonly use a process manager alongside a separate reverse proxy. section 27.3.1

Figure 27.9 In Linux, it’s common for a reverse proxy to be on a different server from your app. The reverse proxy forwards incoming requests to your app, while a process manager, such as systemd, monitors your apps for crashes and restarts it as appropriate.
CH27_F09_Lock3

Use the deployment diagram to distinguish request forwarding by the reverse proxy from crash monitoring and restarting by the process manager. section 27.3.1

How ASP.NET Core in Action, 3e covers it

How deep it goes
Explains monitoring and restart responsibilities, but does not provide process-manager configuration steps.
Examples
Uses systemd on Linux and IIS on Windows as examples of process-management arrangements.
What you can do after
Configure a process-management tool to monitor an application and restart it after crashes or unresponsiveness.
How it connects
Connects process managers with reverse proxies, IIS, Linux, systemd, and Docker.

Also explained in

Compare how 2 books explain process manager →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of ASP.NET Core in Action, 3e. The section links point to the parts of the book it draws on.