“I need to thank Kong for all their support as we were implementing this project," Viers said. "We would run into a snag or search for the best way to do something, and the team would hop on Slack with us and guide us to the answer so quickly.” 

Viers also revealed insights, keys to success, and lessons learned for getting the most from Kong Konnect’s capabilities.

• “All of the Kong Konnect functionality is easy to discover and explore just through the GUI. If you were a one-man shop, you could run the whole thing basically from here with very little actual coding or API requests at all.”

• “The available plugins are easily configurable. I’ve only had to pick up the smallest amount of Lua to configure them, and they are all manageable via the API.”

• “Not only does everything in Kong have an API, almost all of them are documented and specified as open API specs.”

• “Kong has fantastic APIs lying around. We had integrated them for our internal admin application, but if you can avoid this complexity, do it. Just manage it in Kong all by itself if your product needs don’t require you to integrate as a third party.”

• “In a live production environment where new consumers are added all the time, it can be very costly in development time to operate. We’ve solved that problem through the use of the Kong Terraform provider.”

• “Kong is a wonderfully flexible tool, but if Kong doesn’t need metadata to route, manage, identify, or configure API traffic for your application, don’t put it there. If it’s not Kong-necessary data, store it somewhere else. This can make things really simple — it has route matching, and that means you can match many resources with a single route.”

• “As engineers, we’re always fighting complexity. You should use the features of Kong to have fewer routes that match more back-end resources. That really scratches my simplicity itch. If something breaks, there are fewer things to fix.”

• “We endeavor to keep our Kong services simple by maintaining a single gateway service with several plugins all tied to it at the gateway level. Kong provides plugins that will let you change your route target per route so that you need not point at the same gateway upstream services for every route in a gateway service.”

Writer’s AI Studio launched in 2024 to much fanfare and publication coverage. With a chance to reflect on the before and after of integrating with Kong Konnect. Viers boils the company’s major payoffs for using Kong Konnect into three high-level areas:

• “First, it makes security easier than it ever was for us before,” said Viers.

• “Second, its plugins allow us to unify our API surface to that which is served on the back end internally.”

• “Finally, it unifies troubleshooting. We have many, many services that interact to deliver a user response. When something goes wrong with a request, they all go through Kong. That means I spend a little less time finding the related logs and traces for a request in our system. Just by unifying where the traffic goes, it has already had an impact. You can go from ‘this is fine’ to ‘the fire’s out’ faster with a Kong API gateway, and that makes all the difference.”  

“If you aren’t using Kong Konnect, I encourage you to do so," Viers said. "Kong has solved a ton of problems with delivering APIs and managing users for us so I can write code for our requests rather than hand coding rate limiters and other meta application work.”