Using Swoole to enable micro-services to self-clone themselves in order to replace complex / expensive / inefficient Dockerization

[fakharak]

As per my analysis, Dockerization is bad both for Agile Development as well as for Horizontal Scaling technique, how / why ?

"Agile Development" Aspect of Issues:
Agile Development depends on separation of concerns for quick and easy development. Dockerization expects developers to learn and apply non-coding tool Dockers and Kubernetese. Those who learn it become expensive most developers, and expect all developers in team to know it. this leaves space only for expensive developers, whereas Docker is not a coding tool. This means even programmers will good skills will be rejected if they do not know Dockerization.

Architectural Aspects of Issues:

• Dockerization is an image-copying technique to scale-out horizontally. Here, it should be remembered that Scaling Up with Asynchrony should always have higher precedence over Scaling out (you should scale out when you have utilized computing-resources at full throttle).
• Dockerization also mix another concern of Isolation which is effectively done at OS Process levvel.
• Dockers load whole execution environment in each container/Docker (instead of installign environment globally per instance/ node). This makes containers a Fatty and Resource-hungry services, not truely a Micro service.
• Docker tries to enable platform-independency which should always come from language itself and which should not be a critical development concern as developers using a programming language should be wellversed to the environment the language works well with.
• Docker boasts Portability: This is not a critical or primary concern, adn can be carried out through other image-copying techniques.

Self-cloning truely Micro Services:
-- Swoole already allows to spin multiple services on different ports on an IP.
-- Using Swoole, we should be able to use remote shell Net/Scp to set up execution environment globally on remote server.
-- Using Swoole, we should be able to deploy new services using Git, and execute / stop existing services on any remote server.
-- Swoole logs the stats of server.

Benefits of self-cloning Micro-services:
-- With that model in market, developers will not be deemed to know complex / expensive Dockers.
-- Scaling-out Horizontally will happen, dynamically at run-time, through programming code.
-- "Micro" services will not require to replicate/load whole execution environment so they will be "Micro"-sized services, in true sense.