Optimizing large parameter passing in a service mesh

An apparatus for optimizing data file passing between a first service and a second service in a service mesh, the apparatus comprising:

• a provider sidecar which receives a first request for the first service, the first request comprising a first data file and stores the first data file in a request data file store;
• a first service which, responsive to the first service using the first data file, requests the provider sidecar to retrieve the first data file from the request data file store, the first service initiating a request for a second service to a provider sidecar associated with the second service, the first data file in the request being replaced by a unique token identifying the first data file in the request data file store;
• and
• responsive to the second service using the first data file, the second service requests the provider sidecar associated with the second service to retrieve the first data file from the request data file store.

A computer program product for optimizing data file passing between services in a service mesh, the computer program product comprising:

• one or more computer-readable tangible storage medium and program instructions stored on at least one of the one or more tangible storage medium, the program instructions executable by a processor, the program instructions comprising:
• program instructions to receive, at a first service, a first request for the first service, the first request comprising a first data file;
• program instructions to store the a first data file in a request data file store, wherein a first hash identifies a first portion of the first data file and a second hash identifies a remaining portion of the first data file;
• responsive to the first service using the first portion of data file, program instructions to retrieve the first data file from the request data file store;
• program instructions to initiate a second request by the first service for a second service, the first data file in the second request being replaced by a unique token identifying the first data file in the request data file store;
• and
• responsive to the second service using the first data file, program instructions to retrieve the first data file from the request data file store.