We performed a comparison between IBM API Connect and Tyk based on real PeerSpot user reviews.
Find out in this report how the two API Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
"The solution is very scalable because it's on the cloud."
"Publishers can easily identify, create, and publish APIs on the developer portal, defining plans, packages, and potentially billing rules."
"WSRR is a powerful component for getting the endpoints."
"The statistics component is easy to use."
"I have found the API Management to be most valuable."
"Since it runs on top of Datapower, all Datapower based custom policies can be utilized and exported to API connect but its not straightforward/simple process."
"The interface is very nice. It makes the solution easy to use and navigate."
"The technical support is good. Whenever we need anything, we have our IT team work with IBM to change whatever requirement is needed."
"The portal for developers that this solution provides has great functionality."
"The feature I find most valuable is that this solution allows us to manage our security."
"The most valuable feature is the load balancing with the circuit-breaker function."
"The scalability is very good. That was a key factor in the selection, like how it could be pushed to high volume and scalability, which seemed to be very good."
"You can set up workflows and write limited pieces of logic."
"It is a good product for API management."
"The new version is very unstable."
"Due to bugs in integration, we have to look for workaround on fixing and using DataPower as gateway."
"The implementation of IBM API Connect is complex, as it's an enterprise solution with many components that require more than one person. It's not a single product that you work on, and this is an area for improvement, but normally, it's good. Having a more structured model for IBM API Connect support is also room for improvement that would help customers better."
"In the next version, I don't know if they've already been included it or not, but the designer and all the tools should be on the cloud. I don't want any external installation or local installation."
"It's based on a little bit dated architecture. A lot of evolution has happened after that. It's an evolving field. Kong is a Kubernetes-based platform. Kong runs on Kubernetes, but all the other ones are in microservices. So, there's a lot of improvement that can be done."
"The installation process could use improvement. I hope that in the next release, the installation process is easier."
"I would like to see support for non-Java based services. We struggle a bit to be able to deploy and connect our .NET services because of things like data types. We had to map a couple of things. For one solution provider, we had to move them to .NET Core before we could use it properly. I would like to see more agnostic tool service platforms rather than moving it more towards Java or open source."
"While Azure API Management offers configurable scalability, IBM API Connect relies on Kubernetes clusters. This might seem manual and require defining cluster instances upfront, but it's completely customizable and not on-the-fly scaling. It's completely custom-driven, not on-the-fly scaling, which some may consider cumbersome."
"We ran it for a while, but then we decided to move away from Tyk, because Tyk's cloud version, the SaaS version, has a significant limitation of limited flexibility, so you can't program very much."
"In terms of our usage, the main area of concern is that they tend to build enhancements slightly ahead of the considerations for what those enhancements and extensions are. So it could be slightly better communication with the customer base that would be my main issue with them."
"It is a young product and does not have the kind of brand recognition that would make it a more popular solution with our clients."
"We would like a better tool for generating documentation for the APIs to be developed."
"Sometimes when new features are released, they are not immediately stable."
"I would like to see some additional features like having some extensions for .NET core because we use it for our back-end language."
IBM API Connect is ranked 5th in API Management with 73 reviews while Tyk is ranked 17th in API Management with 6 reviews. IBM API Connect is rated 8.0, while Tyk is rated 7.6. The top reviewer of IBM API Connect writes "Good speed and performance, but it's based on a bit dated architecture". On the other hand, the top reviewer of Tyk writes "Simple to install, has many features, but lacks support for multiple programming languages". IBM API Connect is most compared with Apigee, IBM DataPower Gateway, Microsoft Azure API Management, MuleSoft Anypoint API Manager and Amazon API Gateway, whereas Tyk is most compared with Apache APISIX, Traefik Enterprise, Apigee, Microsoft Azure API Management and Zuplo. See our IBM API Connect vs. Tyk report.
See our list of best API Management vendors.
We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
