Critically Urgent: Cloud Deployment Architecture for Swoole in Multi-process / Multi-threaded Mode

[fakharksa]

Please answer these questions before submitting your issue.

1. What did you do? If possible, provide a simple script for reproducing the error.

Development using Swoole in Multi-process mode, instead of Base (single process) mode

2. What did you expect to see?

I expect to see an offering on a Third-party Cloud that can offer multi-process (non-Containerized) Deployment Architecture which fits to my multi-process requirements ? like, dedicated CPU Cores OR vCPUs (I think in Third-party Clouds, the "vCPUs" are more like OS-Threads, but not actual CPUs).

If no Cloud offers such Multi-process / Multi-threaded Deployment Architecture, then advise if we should go for a on-premise Deployments ? tailored to our custom needs.

3. What did you see instead?

I feel that Containerized Deployment Architecture may not fit to such multi-process / multi-threaded architecture (like Swoole in Multi-process mode, Go Lang, Netty / VertX (Java / Kotlin) and .NET (Core) ), because a Container maps to one single OS-process; a container can not offer a multi-process architecture. (I further think that in order to simulate multi-process architecture from Containers, we have to use multiple containers with gRPC / HTTP2 between them which has network layer over-heads and has management / DevOps cost).

4. What version of Swoole are you using (show your php --ri swoole)?

5.1.3

5. What is your machine environment used (show your uname -a & php -v & gcc -v) ?

Ubuntu 22

[praswicaksono]

You can easily deploy multiprocess swoole in your vps/hardware right? I think you can utilize some deployment script like deployer to deploy to multipler server if needed