Cross-jurisdictional microservice-based cloud platform deployment

1. A method, comprising:

receiving, by an orchestrator device in a first cloud platform in a first jurisdiction, a request from a first module deployed in a second cloud platform in a second jurisdiction,

wherein the first jurisdiction and the second jurisdiction are associated with different jurisdictional characteristics related to restrictions of data transmission external to the first jurisdiction and the second jurisdiction,

wherein information associated with fulfillment of the request includes at least a first portion that is compliant with a jurisdictional characteristic of the second jurisdiction, and a second portion that is not compliant with the jurisdictional characteristic of the second jurisdiction, and

wherein the request, received by the orchestrator device, includes the first portion and does not include the second portion;

processing, by the orchestrator device, the request in order to identify a second module deployed in the first cloud platform to which to forward the request;

receiving, by the orchestrator device, a token confirming receipt of the second portion within the second cloud platform;

forwarding, by the orchestrator device and to the second module, the token to indicate that the request is to be fulfilled without the orchestrator device receiving the second portion;

forwarding, by the orchestrator device, the request to the second module to enable fulfillment of the request;

receiving, by the orchestrator device, a response from the second module,

wherein the response is compliant with a jurisdictional characteristic of the first jurisdiction;

identifying, by the orchestrator device and based on processing the response, a third module deployed in the second cloud platform to which to forward the response; and

forwarding, by the orchestrator device, the response, to the third module.

2. The method of claim 1 , wherein the first cloud platform and the second cloud platform are separated by a jurisdictional firewall.

3. The method of claim 1 , wherein at least one of the jurisdictional characteristic of the first jurisdiction or the jurisdictional characteristic of the second jurisdiction is an information privacy requirement.

4. The method of claim 1 , wherein the first cloud platform is co-located in the first jurisdiction with a first interface to one or more systems in the first jurisdiction, and the second cloud platform is co-located in the second jurisdiction with a second interface to one or more systems in the second jurisdiction.

5. The method of claim 1 , further comprising:

receiving, via an interface in the first jurisdiction, one or more commands relating to one or more development operations tools; and

controlling the second cloud platform in the second jurisdiction based at least in part on receiving the one or more commands relating to the one or more development operations tools via the interface in the first jurisdiction.

6. The method of claim 1 , further comprising:

monitoring, by the orchestrator device, one or more microservices of at least one of the first cloud platform or the second cloud platform.

7. The method of claim 1 , further comprising:

confirming receipt of the second portion within the second cloud platform; and

providing data indicating that the request is to be fulfilled without the orchestrator device receiving the second portion.

8. A device, comprising:

one or more processors to:

receive a request from a first module deployed in a second cloud platform in a second jurisdiction,

wherein the device is associated with a first cloud platform in a first jurisdiction,

wherein the first jurisdiction and the second jurisdiction are associated with different jurisdictional characteristics related to restrictions of data transmission external to the first jurisdiction and the second jurisdiction,

wherein information associated with fulfillment of the request includes at least a first portion that is compliant with a jurisdictional characteristic of the second jurisdiction, and a second portion that is not compliant with the jurisdictional characteristic of the second jurisdiction, and

wherein the request, received by the device, includes the first portion and does not include the second portion;

process the request in order to identify a second module deployed in the first cloud platform to which to forward the request;

receive a token confirming receipt of the second portion within the second cloud platform;

forward, to the second module, the token to indicate that the request is to be fulfilled without the device receiving the second portion;

forward the request to the second module to enable fulfillment of the request;

receive a response from the second module,

wherein the response is compliant with a jurisdictional characteristic of the first jurisdiction;

identify, based on processing the response, a third module deployed in the second cloud platform to which to forward the response; and

forward the response to the third module.

9. The device of claim 8 , wherein the first cloud platform and the second cloud platform are separated by a jurisdictional firewall.

10. The device of claim 8 , wherein at least one of the jurisdictional characteristic of the first jurisdiction or the jurisdictional characteristic of the second jurisdiction is an information privacy requirement.

11. The device of claim 8 , wherein the first cloud platform is co-located in the first jurisdiction with a first interface to one or more systems in the first jurisdiction, and the second cloud platform is co-located in the second jurisdiction with a second interface to one or more systems in the second jurisdiction.

12. The device of claim 8 , wherein the one or more processors are further to:

receive, via an interface in the first jurisdiction, one or more commands relating to one or more development operations tools; and

control the second cloud platform in the second jurisdiction based at least in part on receiving the one or more commands relating to the one or more development operations tools via the interface in the first jurisdiction.

13. The device of claim 8 , wherein the one or more processors are further to:

monitor one or more microservices of at least one of the first cloud platform or the second cloud platform.

14. The device of claim 8 , wherein the one or more processors are further to:

confirm receipt of the second portion within the second cloud platform; and

provide data indicating that the request is to be fulfilled without the device receiving the second portion.

15. A non-transitory computer-readable medium storing instructions, the instructions comprising:

one or more instructions that, when executed by one or more processors of a device, cause the one or more processors to:

receive a request from a first module deployed in a second cloud platform in a second jurisdiction,

wherein the device is associated with a first cloud platform in a first jurisdiction,

wherein the first jurisdiction and the second jurisdiction are associated with different jurisdictional characteristics related to restrictions of data transmission external to the first jurisdiction and the second jurisdiction,

wherein information associated with fulfillment of the request includes at least a first portion that is compliant with a jurisdictional characteristic of the second jurisdiction, and a second portion that is not compliant with the jurisdictional characteristic of the second jurisdiction, and

wherein the request, received by the device, includes the first portion and does not include the second portion;

process the request in order to identify a second module deployed in the first cloud platform to which to forward the request;

receive a token confirming receipt of the second portion within the second cloud platform;

forward, to the second module, the token to indicate that the request is to be fulfilled without the device receiving the second portion;

forward the request to the second module to enable fulfillment of the request;

receive a response from the second module,

wherein the response is compliant with a jurisdictional characteristic of the first jurisdiction;

identify, based on processing the response, a third module deployed in the second cloud platform to which to forward the response; and

forward the response to the third module.

16. The device of claim 15 , wherein the first cloud platform and the second cloud platform are separated by a jurisdictional firewall.

17. The device of claim 15 , wherein at least one of the jurisdictional characteristic of the first jurisdiction or the jurisdictional characteristic of the second jurisdiction is an information privacy requirement.

18. The device of claim 15 , wherein the first cloud platform is co-located in the first jurisdiction with a first interface to one or more systems in the first jurisdiction, and the second cloud platform is co-located in the second jurisdiction with a second interface to one or more systems in the second jurisdiction.

19. The device of claim 15 , wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

receive, via an interface in the first jurisdiction, one or more commands relating to one or more development operations tools; and

control the second cloud platform in the second jurisdiction based at least in part on receiving the one or more commands relating to the one or more development operations tools via the interface in the first jurisdiction.

20. The device of claim 15 , wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

monitor one or more microservices of at least one of the first cloud platform or the second cloud platform.