I have an idea. Bring the concept of microservices into software! Within software module interfaces that can only communicate with one another via socket like

I have an idea. Bring the concept of microservices into software! Within software module interfaces that can only communicate with one another via socket like serial interfaces with no type checking! Or simply have all your software modules running as forked processes on the same hardware and have them all communicate with one another via sockets or http. That means every software module must be it's own server! To further imitate microservices, make sure that code in one software module can never ever be moved to another software module. Make it hard to reorganize things. Also make sure teams can only ever work on one section of the code base. Does the above make any sense to you? If it doesn't make any sense to you it's probably because code organization using microservices doesn't make any sense period because the examples above are literally doing the same thing in software that is done in hardware. If it does make sense to you, then why are you using microservices to add extra complexity to the code? If you can do the same in software then you'd be doing the exact same thing as the hardware equivalent minus the extra complexity of multiple containers or VMs. Don't use hardware to organize code, use code to organize code and use hardware to maximize performance.