I’ve been working with postman for a while and love it - I’ve also been using some of the postman-echo’s delay to do some tests. I’ve been working on a project in Twilio Studio that requires us to wait for a while before moving on to something else - we can’t really do this easily or at scale without invoking an API that waits a couple of seconds before returning - I thought, why not use postman-echo! https://postman-echo.com/delay/3 is a great example.
Now I’m on the forum to see whether the postman-echo delay is appropriate for our own uses - we’d be working with the delay functionality on up to max around a hundred concurrent invocations, but likely to be much less on average, with us only using the system for part of the day.
Is this ok? I feel like the servers can handle it but I’m wondering on a couple of things:
- Are the servers up 24/7, and if so, is there any chance the API will not work at any point?
- Does this violate any terms of using the API (using it in my own environment for work)
Currently, the alternatives would be to deploy and run my own service, however having yet another thing to maintain is not appetizing right now.
Let me know if there’s any more information you need!