Hello Community,
We are currently using Appian for BPM-related processes, but recently we have started utilizing Appian as a backend service to handle multiple API requests in one of our services. We've defined REST services in Appian, and our clients are now calling these APIs, essentially treating Appian as a web server.
However, we are facing some performance challenges, including timeouts and long response times. We also conducted load testing, and the results were below our expectations in terms of performance under heavy loads.
My question is: based on your experience, is Appian designed to handle high API request loads in this manner (i.e., functioning like a web server)? Should Appian be used for such purposes, or should this approach be avoided due to potential limitations in handling large-scale API traffic?
Any best practices, optimization tips, or insights on the suitability of Appian for this use case would be greatly appreciated!
Thank you in advance!
Discussion posts and replies are publicly visible
Once we have designed a similar application and we witnessed slowness and performance issues. Thing is that, we can use start process to utilize load balancer but to get the output back from processes as request response we had to make use of activity chaining. Appian is not meant for such design, even the same is mentioned in docs/best practices also.