Marg Kong

The documentation is well-organized. Getting things running in Docker as a test was very easy. It has many potentially useful features.

I understand Mashape had Cassandra running already, but it's a ridiculous requirement for a configuration store.

We switched to Nginx.

No worries about implementation, Takes very little time to setup and get things running. I was using way2sms api to send sms for my project work. I used their python library which was great

I was a bit doubtful about the auth system. which involved sending the sms text, and login credentials as url parameter in the GET request.

I used a very small portion of serrvice that kong provides and i was pretty happy :

I was trying to implement phone verification using sms

1. Plugin based Architecture help to extend faster

2. Build on top of Nginx prove it to be satble in production

3. Lua Scripting Language make it easy to understand write code for Kong

4. Quick support community on Slack

1. Lack of a Official UI or Administration Panel

2. Lack of built-in analytics at small scale

3. Lack of policies structure to be applied to multiple consumers

4. Non Cassandra DB support

Must consider evaluating its available UIs or admin interfaces before going live. Since in live environment, you can't actually go to your notes and look for curl commands.

We needed to publish our REST APIs to our partners and later utilize same APIs to be consumed for our mobile products. So we need to implant an API gateway which helps us to stream line our APIs development to deployment process.

With kong we can avoid writing lot of similar code on each API, like rate limiting and logging.

Kong is wonderful if you enjoy Lua with Openresty and look to have an sll-in-one solution for API implementation and management. Lua is not as popular as it should be, but Openresty has proven performance and a strong community. For developers using either (likely both technology, Kong is exciting and fun to implement.

Documentation is also spectacular. Many of the tools within their ecosystem is open source, and usage is free for smaller use cases. They are one of the biggest sponsors of Openresty, so the developer community is pretty active as well.

While Kong is great for implementation of API's, a more manual implementation using serverless is usually the path most devs go for. Kong's use case is a bit too specific to bring over most modern microservice devs to the table. This really limits Kong to just large enterprise contracts which likely do not have as large of a consumer base due to the usage of Lua.

serverless will be easier to hire developers for if you are looking for long-term implementations.

I found Kong looking for active products implementing Openresty. I assume 90% of kong's customers also do the same.

What do you like best?

What do you dislike?