Layer7 API Management vs Tyk comparison

"The product supports more than just HTTP protocols; it also caters to JMS and FTP protocols."

"The security checking authentication is our primary use case for this solution."

"The scalability has been good. We haven't had to scale up a whole lot, even with all the extra transactions we're running through it. We're in the area of about 2 and 1/2 million OAuth tokens issued per hour, and it's performing fine with that."

"This product, at first blush, looks something like it's one of those weekend warrior tools, but it's not. It's an enterprise-class tool with the kind of usability that you wouldn't expect. And with that usability - how do you have your cake and eat it too? Well, it's because of the product's extensibility. It's very well-integrated with your existing Java library of processes and procedures, as well as your ability to write new extensions to it. You get so much of the base functionality but you don't give up the ability customize."

"The Mobile API Gateway is also great."

"API Management makes dealing with APIs easier. It'll help you to move ahead on your API application journey. The solution allows developers to create more advanced security policies"

"Simple to use and easy to develop APIs."

"The latest version that just came out at the first of October really was a powerful move in the right direction. I was very, very pleased with that because it allows now beginning to use information of things. We've got this IOT infrastructure that we can plug into, and for my use cases there are a lot of outdoor sensors that provide valuable information to my customers."

"It is a good product for API management."

"The portal for developers that this solution provides has great functionality."

"You can set up workflows and write limited pieces of logic."

"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."

"The feature I find most valuable is that this solution allows us to manage our security."

"Layer7 API Management could improve by assing more portal-based capabilities."

"From the last version, they have added more dashboard support, but there is still a lot they need to improve. In terms of monitoring, it's almost all covered. The interface can be improved, though."

"The product's initial setup phase is not very straightforward, making it an area where improvements are required."

"One of the features that the tool provides is the ability to simply onboard new APIs to an existing security platform. We build all the policies for security upfront, and then we can add those policies pretty simply and straightforwardly to any new API that gets developed in the enterprise."

"There are old algorithms that the tool does not support - and it shouldn't, in my opinion. But sometimes customers need old algorithms, from old use cases and old applications, migrated to the platform. At those times, there are hiccups that happen."

"The developer portal needs to fully supported SOAP services (including WSDL publication with security), it would certainly push adoption for us."

"One area where it certainly needs to improve is the way it allocates requests, in terms of rate limiting. Also, there is no native Kafka connectivity."

"One specific feature that we need is the ability to authenticate directly to the server with API data. It's not complex nowadays. This is a feature that we need and CA doesn't have it."

"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."

"I would like to see some additional features like having some extensions for .NET core because we use it for our back-end language."

"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."

"Sometimes when new features are released, they are not immediately stable."

"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."

"For what we are after, the pricing is okay. It is competitive."

"If you do a TCO of more than five years, then you will see a big jump in costs for some vendors."

"It has a reasonable pricing model by instance."

"It is a pricey product, although not extremely overpriced compared to competitors in the market."

"Purchase 4.0 now and wait until they flush out the 4.1 problems."

"There is an annual license for the use of this solution. I think we are paying for some support maintenance fees, included in that license. I don't know how it works. They should provide more information."

"There are some costs for maintenance that we are charged, but that seems fair because we get the support."

"It depends on your use case of course, how much you want to go with that, because it can get pricey and depends on the size of your company."

"We are using the open-source version of this product, so there are no licensing costs for its use."

"It had a free version, which suited many of our needs, but not all, but we were happy to go ahead with the licensed version as well, which is the paid version."

"The cost curve is far smoother, both in terms of volume and the number of calls it's running on, compared to most competitors. So it's a tad more expensive at the very low end, but the curve is nothing like Apigee or some of the others."

"The price is low compared to other products of a similar type."

"There are different versions and plans available depending on the requirements, so there is flexibility in terms of the pricing."