Hacker News Reader

Exactly this. Sometimes I will have multiple entry points (app, celery, &c.), but each process is always launched in a separate container.

View on HN

I would argue, service, not process :-)

You could certainly make that argument, but I've struggled to think of cases where processes aren't the right point of container separation.

Nginx, Apache Prefork, Apache MPM, and PHP FPM all have multiple processes, and I would NEVER try to split up subprocesses of any of these into multiple containers.

It's quite simple if something communicates through shared memory, it should probably be in the same container. If it doesn't then that's NOT a reason to keep it in the the same container, but I don't see how it justifies the work of splitting it up....

Yeah, worker processes are the only thing I can think of. Even then, It is often more flexible to just run one process containers and have more of them. Then you can allocate containers more flexibly.

Absolutely for anything that uses shared memory for IPC, but then you basically have threads pretending to be processes. ;-)

Reply on news.ycombinator.com