The benefits and trade-offs associated with the service per process style are as follows:
- This approach helps in separating the runtime processes on which the services run. Thus, it creates an isolation between the services, so that a memory leak or fat exception in one process does not affect the other services to some extent.
- This allows for selective scaling of service, by allowing more deployments of a service compared to other services on the existing hardware.
- It also gives the freedom to teams of using a different application server/web container based on specific use cases or the needs of the team.
- However, it cannot prevent any one service from hogging system resources (such as CPU, I/O, and memory) that ...