concept single process in category elixir

This is an excerpt from Manning's book Elixir in Action.
For example, if you’re implementing a web server that manages multiple to-do lists, you most likely have one server process for each to-do list. While handling an HTTP request, you can find the corresponding to-do server and have it run the requested operation. Each to-do list manipulation runs concurrently, thus making your server scalable and more performant. Moreover, there are no synchronization problems, because each to-do list is managed in a dedicated process. Recall that a single process is always sequential, so multiple competing requests that manipulate the same to-do list are serialized and handled sequentially in the corresponding process. Don’t worry if this seems vague — you’ll see it in action in chapter 7.
Here, each box represents a single process. The Clients boxes are arbitrary clients, such as HTTP request-handler processes. Looking at this diagram, you can immediately spot some characteristics of your system’s concurrent behavior:

This is an excerpt from Manning's book Elixir in Action.
Processes are light. It takes only a couple of microseconds to create a single process, and its initial memory footprint is 1 to 2 KB. By comparison, OS threads usually use a couple of megabytes just for the stack. Therefore, you can create a large number of processes: the theoretical limit imposed by the VM is roughly 268 million!
Here, each box represents a single process. The Clients boxes are arbitrary clients, such as HTTP request-handler processes. Looking at this diagram, you can immediately spot some characteristics of your system’s concurrent behavior: