To me, the most valuable feature of 3scale API Management is that it lets you add a backend to the product.
I also like that you can integrate it well with OpenShift clusters, making 3scale API Management a useful solution.
We tried to use the portal, but we decided that it wasn't enough. The content management system (CMS) is not easy to use if you want to customize things, and it's hard to get someone who has the knowledge to work with the CMS.
Sr. Enterprise Architect at a tech services company with 501-1,000 employees
Nov 14, 2022
What was suggested by Red Hat was a crucial part of the configuration, but when we started to ask about the supportability of this configuration, Red Hat said only some parts of the configuration would be supported.
I believe the CMS part of it has room for improvement though. That is where you write a couple of things if you want to publish your API. It's based on liquid scripting, which doesn't seem like the obvious ones to script with.
What I'd like to improve in 3scale API Management is its route-limiting feature. Currently, I don't know how to do that effectively on the solution, but in Kong, I know how to do it, so I would love to see route-limiting being easily done on 3scale API Management.
It would also be good if there was some authentication that you could do from 3scale API Management because Kong offers that functionality out of the box.
What I'd love to see in the next release of 3scale API Management is the ability to integrate more plug-ins easily onto the platform, so you'll be able to extend it, and even do customs management. If Red Hat could offer that extension where it allows the internal organization where 3scale API Management is deployed on-premise to integrate its tools on top of 3scale API Management and provide an API for that, that will make the solution very powerful.
