If I get your requirement correctly, you are trying the get the DATA of the first call in the subsequent calls, identified by the UUID.
If I got it correctly, then yes, there is a concept of cache in the Apigee Edge, which you can use. You can set the data in the cache in the first call and associate the UUID. And in the subsequent calls, you can pass the UUID and get the data from the cache and process it further
You would find required information to populate the cache here and to look up the cache data here
Yes, it should work well for parallel calls with different UUIDs. That means, in the system, there are multiple UUIDs having same or different data. This should work perfectly well.
Knowing that Cached data is stored in machine memory, so the cache can store data “up to the memory capacity of the virtual machine”, which means it’s not precisely specified.
What about having millions of users requesting these APIs, and for each request, we are creating a keyFragment for 5 min…
is there any limitation on creating these caches? @anil sagar @meghdeep Basu