The Motley Fools Site Operations Tech team supports a diverse set of front and backend development teams by providing tools, training, and troubleshooting of code-level and infrastructure issues. Infrastructure under the teams management includes CDN, WAF, DNS, and the tools relevant to API management.

As The Motley Fools teams embraced microservices to reduce the time to market for adding or modifying services, the Site Ops Tech team knew they needed an API gateway to provide dynamic, synchronous experiences regardless of client channels.

As an interim solution, we built a simple API gateway with OpenResty and NGINX, said Tyler Reber, systems engineer and lead on Kong setup. It was a strict solution to solve a particular problem we faced at the time, and it was not broad enough to include common requests we received from service teams around authentication and caching for services.

While the interim solution could proxy traffic and apply basic management policies, the team was increasingly receiving requirements that demanded custom development.

One team wanted to implement an Alexa skill that required OAuth, said Nick Travis, Site Ops Tech lead. We did not have the bandwidth to code that in-house, so we needed to bring in a third-party partner, which delayed time to market for getting the service.

The interim solution also did not help expose APIs that existed across The Motley Fool.

It took a lot of brute force for developers to find our APIs searching their code and others code, guessing -api in GitHub, scrolling through Slack channels, Travis explained. For the documentation that did exist, some used OpenAPI specifications, but others were just a JSON blob.

With the number of requests continuing to accumulate and no way to easily expose APIs and ensure their quality, The Motley Fool team began to explore new solutions.

The team initially explored Kong due to its familiarity with Kongs lightweight underlying architecture.

We saw that Kong could do everything we considered in our core feature set for next-generation API management and all with a very small configuration file, said Travis. We wanted to aggregate where APIs flow, track their utilization, manipulate them in-flight, and understand how policies like authentication and caching could work within the solution.

In evaluating Kong, the team quickly saw a path to reducing custom development and satisfying demand from its service teams.

Kongs plugin architecture was especially appealing, said Reber. Rather than needing to custom code for commonly requested services like proxy caching, we could simply apply these policies out-of-the-box.

Travis and the team at Motley Fool also valued Kongs extensibility and active developer community, built on an open source foundation.

The team also appreciated Kongs deployment flexibility, performing well across cloud, on-premise, and hybrid scenarios.

In the past, we had tried a cloud-based API management solution. We sunsetted that because it was costly and not aligned with our requirements, said Mike Shade, DevOps engineer. Most of our environment is on-premise, but due to the size of its configuration file, we saw a lot of latency when deploying changes.

After a short POC, the team moved into implementing Kong as its API management solution.

With Kong, The Motley Fool has greatly improved the experience for developers across the organization. The teams solution will live on The Motley Fools on-premise environment, proxying hundreds of services and billions of API calls annually.

With the solution in place, the team can take advantage of out-of-the-box policies for common enterprise requirements, preventing the need for extensive custom development. We are excited about Kongs canary release plugin, said Shade.

Kong Enterprises out-of-the-box plugins for advanced routing, advanced proxy caching, OpenID Connect, and several other types of authentication are also relevant for us.

Beyond managing APIs, the team also found value in how APIs are documented with Kong.

With Kongs Dev Portal, we are aggregating the API experience so developers understand what is out there and being used, said Travis. This is a self-service solution, which will increase in value as we show more and more people the benefits of getting their APIs well-documented and into the portal.

Kong enabled The Motley Fool team to modernize its approach to API management. Rather than needing to rely on custom development, the team can apply policies out-of-the-box. Traffic outside and within the platforms cluster is unified under a single gateway, reducing latency and improving the experience for development teams across the organization.

Kongs enterprise support has been critical for us, said Shade. We rely on this support, and knowing there is a great team behind us that has been supporting products like this for a long time is key.

Kongs support gives The Motley Fool team confidence in managing traffic for mission-critical services, even in periods of sometimes unpredictable peak demand. For a company all about making smart financial decisions, The Motley Fool team is glad Kong has proven itself a valuable investment.