The common elements of the use case are a medium to a high volume of API calls, generally in a Microsoft-based environment, and occasionally Amazon. Implemented on the public cloud primarily for financial institutions.

Serving retail clients with a reasonably complicated system architecture involving legacy technology and a variety of more modern administration services and systems. Then, the full customer service frontend, where we've got the design interface plugged into the customer journey flows, makes those somewhat dynamic with a standard render forward from the CNA.

What we have been trying to do is reveal APIs for some businesses that we're trying to create that still use some of our legacy platforms and incorporate the newer technologies that we're trying to bring on.

We are a solution provider and Tyk is one of the solutions that we implement for our customers. It is an API gateway and management system that is the single entry point for all of the microservices.

We use this solution to measure, and eventually scale our application programming interfaces.

I am a back and front end developer and I have a great experience with Tyk Management. We mainly use it to manage our APIs. We have API introductions for our customers.