Is there a way to manage a session between apigee edge and back end system between multiple request which goes through apigee edge platform to backend.
Solved! Go to Solution.
Will add to what @sudheendra suggests.
Yes. Keep it stateless, as much as possible. If you can't, I suggest a few options:
Let us know your thoughts!
By default the API proxies you create in Apigee Edge are stateless. So they don't maintain any state by design. But you could use Cache or Key-Value-Map (KVM) policies to maintain state. You could also leverage API BaaS (datastore) to store the session information across multiple requests.
Hi @Sudhee Sreedhara, @Diego Zuluaga I was wondering about this question too. It's there a performance benchmark between apigee KVM vs Redis or another inMemory tool ?
How can i do this. any examples or reference links
there multiple incoming requests into my apigeeproxy
firstime - a req.id comes - i need to store in somewhere
next time another req comes with same req.id - then i need to route it same load balancer target, which it is going to first.
Will add to what @sudheendra suggests.
Yes. Keep it stateless, as much as possible. If you can't, I suggest a few options:
Let us know your thoughts!
User | Count |
---|---|
1 | |
1 | |
1 | |
1 | |
1 |