This post is the last in a three-part series about deploying Kong as a service mesh. The first post discussed how we define the term “service mesh” here at Kong, and the second post explained the architectural pattern used to deploy Kong as a mesh. In this post, we will talk about the new features and configuration options we added to give Kong its mesh capabilities.
APIs securely expose key enterprise data and services to internal stakeholders and external developers. They can also generate a goldmine of data. As you grow your API programs to reinvent operations, build modern applications, and create ecosystems, you can also use key API data to answer some important questions: Which customers are using my APIs? How do I categorize my customers? Should I monetize my APIs? How should I build my API revenue model and rate plan?
Application programming interfaces (APIs) are both the glue between systems, data, and applications and the mechanisms that let developers leverage functionality and data for new purposes.
