An Apigee customer asked me for advice on how to implement a requirement. I want to see what the community suggests:
We have a requirement to call a backend system in a loop and put the responses together and send to the client. Each loop in this case might take several seconds as it’s hitting a legacy backend. It’s a mix of orchestration and looping where each loop makes two different calls to the backend and puts the responses together and then again mashes the responses after the looping.
They use Edge and have an enterprise service bus. There is debate about where to put this logic. Does it belong in the service bus or would it make sense to implement it in a JavaScript policy or maybe a Node.js application? How do you feel about having complex logic in Edge? Does your team find it’s easy enough to test, debug, and maintain the code?
LinkedIn
Twitter
