Using Appian as a Backend for High Volume API Requests - Best Practices and Performance Considerations?

Question

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!

Kumar Agniwesh · Answer

In my opinion using Appian to be used as webserver would be over stretching Appian limitations. Yes it can do that, but should we be using Appian for that ? if you have to use anyways have you considered upgrading the hardware to improve the performance. 
 Appian is also coming up with EPEx for high amount of processing in near future and that would improve the performance to great extend. you can read about that 
 Autoscaling for Process Execution (EPEx)

Soma · Answer

Agreeing with Stefan, this is not an ideal problem statement that Appian as a platform is intended to solve. Please contact Appian Support to get more information and suggestions.