
Kong API Gateway makes life easier will all the existing capabilities that it provides through its user interface for Configuring Services, routes along with handling SSH requirements through Kong itself. It also helps in having a constant access to client servers that are on SSH but needs to be accessed while developing solutions to integrate with the apis where the ips are not static. This is one case that we use kong regularly for. I like the Request Transformation and Response Transformation feature of Kong the most. Its real pain doing that with other API Gateway solutions. If we go with native way of handling Request or Response transformations with Spring Cloud API Gateway etc.. we end with many issues that takes hell a lot of time to fix but with Kong it doesn't need to be deployed every time and with a save everything gets updated and fixing it is also gets easier and requires less effort. Also the logs of kong are also pretty much descriptive about the errors that we face in the Request routing failures, request tracking, identify the reason for failures etc.. Review collected by and hosted on G2.com.
Currently I dont have any dislikes regarding Kong API Gateway and I have worked with Community and Enterprise versions and never found any issues using it. It makes our life simple. I have recommended it at many places wherever there was a need to introduce API Gateway solution. Review collected by and hosted on G2.com.