Tyk Cloud, Hybrid & Self Managed API Management

As a platform architect for contact center solutions, TyK serves as the primary Middleware & API Gateway/Proxy between Genesys Cloud, Salesforce, and other back-end systems at the company.

All customer lookups from the customer front-end portal are converted into REST calls to the back-end system and CRM when customers reach and identify with a particular number. Tyk is being used as an API Gateway via REST interfaces. Similar integrations include converting voice input into a string using Tyk back-end speech APIs, such as Google Cloud Speech-to-Text or Azure Speech Services. The concept remains the same: the front-end passes input, authenticates via OAuth2, and sends it to the back-end; the back-end does the reverse. In some use cases, the input could be decoded and encoded.

The interface has been managed primarily by developers and system analysts from the middleware team, who have configured specific message inputs. It appeared convenient and user-friendly for their agile delivery processes

Flexibility, cost efficiency, and scalability are some of the strategic key benefits worth mentioning

From a security perspective, the authentication methods we have been using and the ability to easily switch between OAuth and OAuth2 are valuable. Tokenization and all pipeline chain controls are important, as is the ability to use standard protocols in the business, such as REST, SOAP, JSON, AsyncAPI, and MCP for AI agents.

Monitoring, logging, and troubleshooting capabilities are quite satisfying

Again, cost is definitely a key factor. A migration from TIBCO middleware to Tyk was driven by cost in many organizations. What I noticed is that the time-to-market was decent, and colleagues were quicker to deliver certain services and new requests from client platforms. It was a positive and smooth experience overall.

Regarding time-to-market, on average, a new service request would arrive within average two sprints when using Agile delivery. It was much quicker and provided an easy way to test in the environment.

Documentation and consultancy could've been better. In the end, we managed to gather all the information and knowledge needed for my integration from various sources. Structured product information that is accessible to the end technical users can add value. Also, tooling for automated generation of the interface descriptions/agreements would be quite valuable

Occasionally, slower performance and glitches may occur, but several factors could be influencing this.

More information on security concepts and development would have been helpful to me. In the new landscape of AI agents and tools, I am not quite sure about governance. I would like to learn more about the governance model and existing out-of-the-box APIs & features to understand how I can enhance them when needed.

Scalability appears to be good based on what I have seen. The API definitions were a little difficult for me to understand, but I am not a developer. There were some problems with rate limits, and in certain cases, the capacity was in question. I believe this has to do with proper scalability and upgrades across the entire cluster, since Tyk itself was not hosted within the company but in the cloud.

I migrated my systems and started using TyK in 2022, marking four years of use.

Tyk is stable and exceeded expectations. Still, certain glitches can occur mentioned earlier

My impression is that Tyk is pretty capable and scalable.

The support is good, but we go through an integrator, so the support is not directly to Tyk as an organization.

The company has been using TIBCO middleware and Data Power for quite some time. It was primarily based on SOAP, not on REST or other services. It was an on-premises solution that worked very well and met the enterprise integration needs, but was occasionally difficult to implement and significantly more expensive than Tyk.

The transition was smooth overall. It was flexible and an open-source product that exceeded my expectations when the migration was initiated and the product was chosen. The migration, which was a phased approach, was positive and flexible. I rate the product between a seven and eight out of ten for overall quality. There are several improvements that I would expect to meet enterprise organization needs, but overall it was a positive experience.

The implementation was handled through a service integrator that my company was working with.

Tyk was cheaper than some alternatives. The cost indications were pretty positive, and the pricing was provided by a third-party supplier.

I would rate Tyk a solid seven (+) out of ten overall.

I have the feeling that I do not have enough information or insight into certain features, but I know that Tyk provides multiple authentication mechanisms, including API keys, OAuth2 (which I used primarily), and basic authentication for some things. With AI and the new world of AI, I believe we will see an increasing need for fine-grained access, down to the endpoint or even the message control protocol level. I know that Tyk has a gRPC gateway that I am not familiar with, and perhaps this is in the right direction. Access lists, customer-specific IP restrictions, and policies are all in the right direction. However, as with any organization, we are still in the early implementation stages and will likely face some challenges. Security has become a major problem. There has been a recent major security breach in which Tyk has also been part of the pipeline.

Regarding AI capabilities, I have limited experience, but I believe Tyk covers the main needs and is a generic product in that sense. I would be curious to learn more about it, and I would be happy to receive more input from the company, or at least a reference where I could find information about its capabilities. For example, how AI could be used in building up services within AI. I cannot provide further input on that yet, but I am open to learning more.

I would expect Tyk and Salesforce to have more specific, service-oriented collaboration. I have noticed some challenges for my middleware colleagues when implementing services and invoking Salesforce and customer custom back-end APIs, though nothing in particular.

What I felt with the implementation of Tyk is that it required fewer senior and more deep experts in middleware development and architecture. A less complicated product implementation meant fewer deep-custom-knowledge experts were needed. This is positive feedback because it looks like a more comprehensive and modern product. In the previous situation, much more deep custom knowledge was required.

My advice would be to have clear use cases and do the homework well in advance. I mean to prepare for the selection process and to look not only at the current set of features but to discuss what is on the roadmap, expected growth, and especially the API needs, how things are going, the cost model, and the licenses. These are generally important inputs for the selection process.

The positive impact was more in terms of understanding because the other tools I evaluated were harder to understand how to use and how to configure. In that respect, I found it much more intuitive and it helped me better understand the concepts and the functioning itself, which I thought was easier to use. I noticed the ease of configuration and the knowledge itself.