I use 3scale API Management in the company I currently work in, but in my previous company, I used Kong.

I'm a consultant for 3scale API Management, so my customers use this product.

I belong to a large organization, and around fifty to one hundred people use 3scale API Management, while twenty to thirty administrators maintain it.

My rating for 3scale API Management is seven out of ten.

I give the solution an eight out of ten.

The solution was an independent product purchased by Red Hat. It's a full-blown API management solution. This I would say considers the majority of the cost of this integration package. This is a very good product, but maintenance-wise and with any skills, you need time and you need a very good understanding of all the moving parts in it because there are many.

There are plenty of things that are not standard about the solution, and you need an understanding of the product and all the subsystems, and their roles in the overall architecture of this product. We had to go through a very diligent exercise with finding out all these details of architecture because we have plenty of SLAs and governmental standards that we need to adhere to. So we needed to understand exactly when it's on, when it's off, and when the specific part is down, what it means. There are a number of SLAs some of them are important, and some of them are not. This information is not available online, and unless we have professional engagement, with the Red Hat team, we would never know the details. It would be very hard to find out the details and that is very crucial. Otherwise, you just install the solution and run it and if you are using it on-prem You will not be able to understand what's going on. Another thing that's problematic is that for each container that we deploy as a subsystem for 3scale initially, again by a pre-sales team, we've been told completely different resource consumption that they will require. When we started to run it, the consumption on OpenShift was much higher for every single technology that they're using to come to complete the set for the 3scale because a number of technologies need to run simultaneously, the number of packages, and that was not a nice surprise, I would say.

My advice would be that if you're a small or medium-sized organization and you don't require extensive customization for your APIs, you can go for the Red Hat solution.

Overall, I would rate it a seven. It should offer more flexibility. Other products allow for drag-and-drop customization and the ability to add scripts or system out statements. However, that is not the case with 3scale API management.

We have some templates which we use to implement the new onboarding services. My team has around 20 people.

Overall, I rate the solution a seven out of ten.

I rate 3scale API Mangement nine out of 10. I recommend purchasing the OpenShift subscription because 3scale isn't as powerful without it. 

I would advise anyone considering implementing 3scale API Management to have a clear current state analysis and to extensively consider and map their requirements. I would rate 3scale API Management five out of ten.

If you want to significantly impact how your developer portal will work, then you shouldn't think about 3scale as your base for the developer portal. If you just want something out-of-the-box, then 3scale would be sufficient. The consideration should mainly be around the portal.

Overall, it's the organizational things that make you succeed or not. We could probably have managed the API transformation path that we're into, trying to go to API-first, even without the gateway, but it would be a bit harder because it wouldn't be a natural thing to have someone proxying all the things that go not only into the infrastructure but also into the organization. That's the crucial part for success with API management. The product has helped us to get there, but theoretically, it could have been done without the gateway as well. It helps, but it's not a silver bullet.

Setting the portal aside, since we have decided not to use it, and just rating the parts that we are using, I would give 3scale a seven out of 10. But we haven't even tried the Fuse part. That could be a strong addition if you want the ability to integrate as well.

I would rate 3scale as a seven or eight out of ten. I've had more issues with supporting it. Also, the CMS and Open API specification issues I mentioned above. Those things could be better or simpler.

This is a product that I like, and have a lot of interest in learning. It is one that I recommend to our clients. 

I would rate this solution a seven out of ten.