Cross-jurisdictional microservice-based cloud platform deployment

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.

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.