Middleware for communication between microservices and monolithic application
Methods, systems, and computer-readable storage media for receiving, from a first entity, a first call, the call being received by a middleware client of a second entity, storing a set of headers associated with a workflow in a request context holder of the middleware client, and determining that a second call is to be executed from the middleware client of the second entity for the workflow, and in response: reading, by a client of the middleware client, the set of headers associated with the workflow, including the headers in a request of the second call, determining an endpoint for the second call, and transmitting the second call for receipt at the endpoint.
1. A computer-implemented method for executing calls between a monolithic application and one or more microservices, the method being executed by one or more processors and comprising:
receiving, from a first middleware client of a first entity, a first call, the first call being received by a second middleware client of a second entity, the first call comprising a set of headers descriptive of a workflow being executed between a monolithic application and a set of services;
determining that the set of headers included in the first call are allowed headers, and in response:
storing the set of headers in a request context holder of the second middleware client, the request context holder storing the set of headers as a key-value pair comprising a key that identifies the workflow and a value comprising the set of headers; and
determining, by the second client, that a second call is to be executed from the second middleware client of the second entity for the workflow, and in response:
reading, by the second middleware client, the set of headers descriptive of the workflow,
including the set of headers in a request of the second call,
determining an endpoint for the second call, and
transmitting the second call for receipt at the endpoint.
2. The method of claim 1 , wherein the first entity is one of the monolithic application and a microservice.
3. The method of claim 1 , wherein determining that the set of headers included in the first call are allowed headers comprises:
comparing headers of the first call with an allow list; and
for each header matching at least one of a header name and a header pattern of the allow list, including the header in the set of headers.
4. The method of claim 1 , wherein reading the set of headers comprises reading the set of headers from the request context holder indexed based on the workflow.
5. The method of claim 1 , wherein determining the endpoint for the second call comprises:
determining a value from a uniform resource locator (URL) register using a relative URL as an index to the URL register, the value comprising a portion of the endpoint; and
providing the endpoint by combining the value and the relative URL into a full URL.
6. The method of claim 5 , wherein the URL register is stored in a URL register cache of the second middleware client and is refreshed in response to a change in the URL register.
7. The method of claim 1 , further comprising applying a resilience configuration to the second call, the resilience configuration being determined based on a set of resilience instances and a mapping that maps a relative URL to one or more resilience instances in the set of resilience instances.
8. A non-transitory computer-readable storage medium coupled to one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations for executing calls between a monolithic application and one or more microservices, the operations comprising:
receiving, from a first middleware client of a first entity, a first call, the first call being received by a second middleware client of a second entity, the first call comprising a set of headers descriptive of a workflow being executed between a monolithic application and a set of services;
determining that the set of headers included in the first call are allowed headers, and in response:
storing the set of headers in a request context holder of the second middleware client, the request context holder storing the set of headers as a key-value pair comprising a key that identifies the workflow and a value comprising the set of headers; and
determining, by the second client, that a second call is to be executed from the second middleware client of the second entity for the workflow, and in response:
reading, by the second middleware client, the set of headers descriptive of the workflow,
including the set of headers in a request of the second call,
determining an endpoint for the second call, and
transmitting the second call for receipt at the endpoint.
9. The non-transitory computer-readable storage medium of claim 8 , wherein the first entity is one of the monolithic application and a microservice.
10. The non-transitory computer-readable storage medium of claim 8 , wherein determining that the set of headers included in the first call are allowed headers comprises:
comparing headers of the first call with an allow list; and
for each header matching at least one of a header name and a header pattern of the allow list, including the header in the set of headers.
11. The non-transitory computer-readable storage medium of claim 8 , wherein reading the set of headers comprises reading the set of headers from the request context holder indexed based on the workflow.
12. The non-transitory computer-readable storage medium of claim 8 , wherein determining the endpoint for the second call comprises:
determining a value from a uniform resource locator (URL) register using a relative URL as an index to the URL register, the value comprising a portion of the endpoint; and
providing the endpoint by combining the value and the relative URL into a full URL.
13. The non-transitory computer-readable storage medium of claim 12 , wherein the URL register is stored in a URL register cache of the second middleware client and is refreshed in response to a change in the URL register.
14. The non-transitory computer-readable storage medium of claim 8 , wherein operations further comprise applying a resilience configuration to the second call, the resilience configuration being determined based on a set of resilience instances and a mapping that maps a relative URL to one or more resilience instances in the set of resilience instances.
15. A system, comprising:
a computing device; and
a computer-readable storage device coupled to the computing device and having instructions stored thereon which, when executed by the computing device, cause the computing device to perform operations for executing calls between a monolithic application and one or more microservices, the operations comprising:
receiving, from a first middleware client of a first entity, a first call, the first call being received by a second middleware client of a second entity, the first call comprising a set of headers descriptive of a workflow being executed between a monolithic application and a set of services;
determining that the set of headers included in the first call are allowed headers, and in response:
storing the set of headers in a request context holder of the second middleware client, the request context holder storing the set of headers as a key-value pair comprising a key that identifies the workflow and a value comprising the set of headers; and
determining, by the second client, that a second call is to be executed from the second middleware client of the second entity for the workflow, and in response:
reading, by the second middleware client, the set of headers descriptive of the workflow,
including the set of headers in a request of the second call,
determining an endpoint for the second call, and
transmitting the second call for receipt at the endpoint.
16. The system of claim 15 , wherein the first entity is one of the monolithic application and a microservice.
17. The system of claim 15 , wherein determining that the set of headers included in the first call are allowed headers comprises:
comparing headers of the first call with an allow list; and
for each header matching at least one of a header name and a header pattern of the allow list, including the header in the set of headers.
18. The system of claim 15 , wherein reading the set of headers comprises reading the set of headers from the request context holder indexed based on the workflow.
19. The system of claim 15 , wherein determining the endpoint for the second call comprises:
determining a value from a uniform resource locator (URL) register using a relative URL as an index to the URL register, the value comprising a portion of the endpoint; and
providing the endpoint by combining the value and the relative URL into a full URL.
20. The system of claim 19 , wherein the URL register is stored in a URL register cache of the second middleware client and is refreshed in response to a change in the URL register.