Integration with backend systems and runtime configuration simplicity enhance operational efficiency
What is our primary use case?
We have used Apache APISIX as a gateway for our backend systems. We have integrated it with our backend system for several banks in Saudi Arabia. This was a client request, so we have worked on it, and now it is deployed for many customers.
What is most valuable?
Apache APISIX is easy to configure. It supports coding for filters and can integrate with many languages. Its configuration at runtime is very easy. You can configure your gateway at runtime without needing to restart the gateway to apply configurations. This is a perfect feature. The service discovery feature integrates with backend systems and provides powerful load balancing. Also, its integration with Keycloak and authorization systems is a valuable feature.
What needs improvement?
The user interface is limited and does not support all features of Apache APISIX. Users must resort to using command-line interfaces (CLI) for certain configurations, which is not practical. Enhanced documentation with richer information on missing features is needed.
For how long have I used the solution?
I have been working with Apache APISIX for about a year and a half.
What was my experience with deployment of the solution?
I faced some problems with the dashboard and user interface as they supported limited items for configuration. Not all features of Apache APISIX were available on the dashboard, so I had to use command-line commands. However, the initial deployment was straightforward and easy to set up.
What do I think about the stability of the solution?
I did not face any stability issues with Apache APISIX. It has been stable during our use.
What do I think about the scalability of the solution?
Apache APISIX is very scalable and fast. We did not encounter any limitations or issues with its scalability.
How are customer service and support?
I did not escalate any questions to technical support for Apache APISIX. I found the community to be very helpful, and the existing documentation met my needs.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
I worked with several backend systems and implemented a cloud gateway developed internally. We moved to Apache APISIX because it was an open-source solution that was easy to configure.
How was the initial setup?
The initial setup was very easy. The configuration could be easily followed, installed, and deployed with several types of deployment options.
What was our ROI?
Our customer's project was on-premises, so we did not measure the ROI. However, if used globally, it could save a lot of investment because of its many start-up features.
Which other solutions did I evaluate?
We considered several open-source solutions, including Kong Gateway and others. We chose Apache APISIX because it is feature-rich and faster than its competitors.
What other advice do I have?
I recommend Apache APISIX to others because of its many useful features. However, the lack of documentation for some features presents challenges. I would rate Apache APISIX an eight out of ten due to these issues.
Which deployment model are you using for this solution?
On-premises
