How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.
We have two approaches to how we use the solution. We own the managed services and the other we have customers take the subscription and we manage it.
We primarily use the solution to manage our APIs.
We have company-wide APIs which are hosted in Niger, and some of the external clients access the applications via the API, and we provide the post-data information. The clients get their data from our larger API.
They're doing integration work between a lot of different on-premises business platforms, like Salesforce and NetSuite. We're doing integration work, but we're putting all of our APIs into the Azure cloud and using that API manager at this time.
We use it to manage the API. We have a backend API with service in the backend. We use API Management in the front to manage the vendors. They can do their own testing. It's quicker for us to put in the specifications so we can knock off the responses. We build the specs and then get an external developer to start the development without the web service being ready. We also use it for the security and for the clock in features.
Our primary use case is to provide API mapping for our clients. We're a customer of Azure and I'm a system analyst.
Our primary use case is for managing internal APIs, for ordering process APIs and in general process APIs, and resource manipulation APIs. We need an API management to get a better overview, and this is one use case with analytics parts. Another use case is security, being able to rotate API keys and to manage access at a signature point. Finally, we also have the developer portals with the self-service capabilities so that developers can request access to APIs through a developer portal and manage their own keys. We are still in the ramp-up phase, so currently we have actively two or three guys using it. We're planning to increase usage. We're in partnership with Microsoft and I'm an enterprise architect.
It's more of a subscription driven consumption based model, where the APIs are developed to connect backend ERP systems such as SAP and deployed into a library for consumption by both internal and external consumers. The APIs are exposed to the consumers that get onto the API gateway and identify the needed API from the library, use the instructions to subscribe, quickly test and connect to the backend SAP to get the expected information/transaction processed. Prior to this solution there was an age old EDI interface solution. This is enabling the customers to be more flexible with their integration architecture and be more agile as it reduces the IT integration dependency and provides a better user experience. This is part of Techwave application modernization strategy to bring solutions that can bring agility and flexibility to customers and be able to decouple business with huge IT dependent solutions. This is helping us to help our customers migrate away from the age old EDI technology to the latest API and microservices based architectures.
We are publishing microservices using API management. We have created various packages and policies that we are applying over there. We have also created a portal for developers so that they can see what we are doing.
We are a software firm and this is one of the solutions that we provide for our customers.
We use the product for managing APIs - for internal as well as for external communication. Furthermore we enable transparency, governance and re-use.
We use the cloud model. Our primary use case is for integration between different systems. There are many use cases for the API management tool, but the most common scenario is integration between different systems.
We all know it's really hard to get good pricing and cost information.
Please share what you can so you can help your peers.