My company gave Kong Enterprise to only one company in the manufacturing sector, and now we are in talks with another manufacturing company. Kong Enterprise is very useful, especially for IoT applications. Palo Alto Networks is also good for IoT applications. Kong Enterprise has a great licensing model. I am scanning capabilities, making it a good tool for infrastructures.
It serves as an API gateway and microservices management platform, facilitating the creation, deployment, and oversight of APIs and microservices. It serves as a solution for measuring requests, managing upstreams, and handling internal APIs within the bank.
Practice Head - Enterprise Integration & Process Automation at Happiest Minds Technologies
Real User
Top 10
2023-08-25T12:20:39Z
Aug 25, 2023
We had worked for a client from the travel industry who wanted to propose an API manager. They had built microservices on Java and another integration tool. They wanted to apply policies, register their APIs in the API manager, and enforce policies and plugins, like client ID, client secret, throttling, rate limiting, and protocol transformation. The client wanted to apply these things to their APIs.
I lead the integration practices in my organization and have been working in integration for the past 16 years, managing API integrations with various API manager tools such as Kong Enterprise. We are primarily using Kong for the API gateway functionality. For example, we've had a couple of mobile applications with outbound traffic where we would use the Kong Enterprise gateway to expose the API by applying authorization, authentication, and other security policies. We have also used Kong for role-based access control mechanism (RBAC) and integrated it with our enterprise directory in order provide it with this form of access control. There was another particular use case in which we performed some customization, as well. In that scenario, we wrote a Lua script on top of Kong to add an AppDynamics plugin to our web server, for observability and monitoring purposes. Kong has been used over a large user base, not only because it's an enterprise application, but also because the mobile applications we worked with were B2C-based in the retail industry, so the number of users was quite high.
Solutions Architect at a financial services firm with 1,001-5,000 employees
Real User
Top 5
2021-10-06T15:03:42Z
Oct 6, 2021
We have several microservices that are secure using Kong Enterprise. Our microservices are managed through Kong Enterprise API management. We have integrated with IDP to secure it. We use multiple plugins that are bundled with Kong Enterprise.
Vice President – Technology and Architecture at a venture capital & private equity firm with 51-200 employees
Real User
2020-11-24T16:35:03Z
Nov 24, 2020
Our primary use case of this solution was a secure API Gateway hosted on public cloud infrastructure. The manageability, deployment architecture options and scalability were key considerations. Kong is great at organising our API ecosystem and providing the required manageability, scalability observability and security. I'm the vice president of technology and architecture and we are customers of Kong Enterprise.
Head of Digital Delivery at a insurance company with 1,001-5,000 employees
Real User
2020-03-25T07:03:00Z
Mar 25, 2020
We define our enterprise architect and Kong has been selected as an API integration layer solution. We deploy in some of the markets if they're ready to go, and some of the markets are not really ready because we have 10 different markets at the moment. It's an API integration layer so that we can expedite our microservices to the market.
Kong delivers a next generation API platform built for modern architectures. With a lightnight-fast, lightweight, and flexible core, Kong delivers sub-millisecond latency across all your services. Kong's is deployment-, vendor-, and pattern-agnostic, allowing you to run your services how you want, where you want, and with who you want - from baremetal to cloud, monolith to microservices, service mesh, and beyond.
My company is a financial company involved in credit card processing. We use the solution for internal IT secure gateway.
We use the solution for managing microservices and in-built APIs.
My company gave Kong Enterprise to only one company in the manufacturing sector, and now we are in talks with another manufacturing company. Kong Enterprise is very useful, especially for IoT applications. Palo Alto Networks is also good for IoT applications. Kong Enterprise has a great licensing model. I am scanning capabilities, making it a good tool for infrastructures.
It serves as an API gateway and microservices management platform, facilitating the creation, deployment, and oversight of APIs and microservices. It serves as a solution for measuring requests, managing upstreams, and handling internal APIs within the bank.
We had worked for a client from the travel industry who wanted to propose an API manager. They had built microservices on Java and another integration tool. They wanted to apply policies, register their APIs in the API manager, and enforce policies and plugins, like client ID, client secret, throttling, rate limiting, and protocol transformation. The client wanted to apply these things to their APIs.
We deploy this solution to our customers who are enterprise companies. We are partners with Kong and I'm the director of engineering.
I lead the integration practices in my organization and have been working in integration for the past 16 years, managing API integrations with various API manager tools such as Kong Enterprise. We are primarily using Kong for the API gateway functionality. For example, we've had a couple of mobile applications with outbound traffic where we would use the Kong Enterprise gateway to expose the API by applying authorization, authentication, and other security policies. We have also used Kong for role-based access control mechanism (RBAC) and integrated it with our enterprise directory in order provide it with this form of access control. There was another particular use case in which we performed some customization, as well. In that scenario, we wrote a Lua script on top of Kong to add an AppDynamics plugin to our web server, for observability and monitoring purposes. Kong has been used over a large user base, not only because it's an enterprise application, but also because the mobile applications we worked with were B2C-based in the retail industry, so the number of users was quite high.
Kong Enterprise was used for standard API gateway use cases for Microarchitecture.
A central API gateway solution.
We have several microservices that are secure using Kong Enterprise. Our microservices are managed through Kong Enterprise API management. We have integrated with IDP to secure it. We use multiple plugins that are bundled with Kong Enterprise.
Our primary use case of this solution was a secure API Gateway hosted on public cloud infrastructure. The manageability, deployment architecture options and scalability were key considerations. Kong is great at organising our API ecosystem and providing the required manageability, scalability observability and security. I'm the vice president of technology and architecture and we are customers of Kong Enterprise.
We define our enterprise architect and Kong has been selected as an API integration layer solution. We deploy in some of the markets if they're ready to go, and some of the markets are not really ready because we have 10 different markets at the moment. It's an API integration layer so that we can expedite our microservices to the market.
We mostly use this as an intrusion prevention system.