What is claimed is:1. A method, comprising:a microservice formatting a request to a process management microservice and to another microservice to perform an operation on behalf of the microservice;validating, by the process management microservice, the requested operation, wherein the validating comprises verifying in the microservices registry that a kernel version of the microservice is compatible with the another microservice and is available based on a state in a state database;based on the another microservice not being of a compatible kernel version of the microservice converting the requested operation by a converter module of the another microservice according to predefined configuration rules;based on the operation being valid, process management sending the requested operation to the another microservice; andupdating a microservices registry with a status of the microservice and the another microservice;based on the another microservice not being of a compatible kernel version of the microservice converting the requested operation by a converter module of the another microservice according to predefined configuration rules.2. The method of claim 1, where communication between microservices happens over a bidirectional API that corresponds in functionality to a system call in tightly coupled computer operating system.3. The method of claim 1, wherein the microservices registry is a centralized database comprising:state data of each microservice, wherein the state data includes whether a resource managed by the microservice is available, has contention, or has an error condition.4. The method of claim 3, wherein each microservice maintains a local registry of its state in addition to updating the microservices registry, and wherein the microservices registry is a single source of truth.5. The method of claim 1, further comprising: a computer operating system, wherein the computer operating system comprises a plurality of microservices that are interconnected by a bidirectional API, and wherein each of the plurality of microservices corresponds to a component in the operating system, and wherein each of the plurality of microservices is dynamically and independently upgraded.6. A computer program product, the computer program product comprising a non-transitory tangible storage device having program code embodied therewith, the program code executable by a processor of a computer to perform a method, the method comprising:a microservice formatting a request to a process management microservice and to another microservice to perform an operation;validating, by the process management microservice, the requested operation, wherein the validating comprises verifying in the microservices registry that a kernel version of the microservice is compatible with the another microservice and is available based on a state in a state database;based on the another microservice not being of a compatible kernel version of the microservice converting the requested operation by a converter module of the another microservice according to predefined configuration rules;based on the operation being valid, process management sending the requested operation to the another microservice; andupdating a microservices registry with a status of the microservice and the another microservice.7. The computer program product of claim 6, where communication between microservices happens over a bidirectional API that corresponds in functionality to a system call in tightly coupled computer operating system.8. The computer program product of claim 6, wherein the microservices registry is a centralized database comprising:state data of each microservice, wherein the state data includes whether a resource managed by the microservice is available, has contention, or has an error condition.9. The computer program product of claim 8, wherein each microservice maintains a local registry of its state in addition to updating the microservices registry, and wherein the microservices registry is a single source of truth.10. The computer program product of claim 6, further comprising: a computer operating system, wherein the computer operating system comprises a plurality of microservices that are interconnected by a bidirectional API, and wherein each of the plurality of microservices corresponds to a component in the operating system, and wherein each of the plurality of microservices is dynamically and independently upgraded.11. A computer system, comprising:one or more processors;a memory coupled to at least one of the processors;a set of computer program instructions stored in the memory and executed by at least one of the processors in order to perform actions of:a microservice formatting a request to a process management microservice and to another microservice to perform an operation;validating, by the process management microservice, the requested operation, wherein the validating comprises verifying in the microservices registry that a kernel version of the microservice is compatible with the another microservice and is available based on a state in a state database;based on the another microservice not being of a compatible kernel version of the microservice converting the requested operation by a converter module of the another microservice according to predefined configuration rules;based on the operation being valid, process management sending the requested operation to the another microservice; andupdating a microservices registry with a status of the microservice and the another microservice.12. The computer system of claim 11, where communication between microservices happens over a bidirectional API that corresponds in functionality to a system call in tightly coupled computer operating system.13. The computer system of claim 11, wherein each microservice maintains a local registry of its state in addition to updating the microservices registry, and wherein the microservices registry is a single source of truth in the configuration.14. The computer system of claim 11, further comprising: a computer operating system, wherein the computer operating system comprises a plurality of microservices that are interconnected by a bidirectional API, and wherein each of the plurality of microservices corresponds to a component in the operating system, and wherein each of the plurality of microservices is dynamically and independently upgraded.