Demystifying Service Mesh: New Pattern or New Technology?

With Kong 1.0, we confirm that Kong is a proven, robust, stable, and production-ready API management platform. Kong stands poised as an API gateway, service mesh, and the basis for a control platform that will serve users faithfully as their information exchange needs, and those of the industry, change.

As the amount of data and services explodes, enterprises must prepare for a cloud-native world that enables them to free and scale their architectures.

In this presentation, Kong CTO & Co-Founder, Marco Palladino, and Director of Ecosystem, Cooper Marcus, walk us through the journey towards Kong 1.0 and share the vision that positions Kong as a service control platform for all of your data flows, regardless of your chosen architecture or deployment patterns.

Webinar takeaways:

- Learn about the three forces leading us towards cloud-native first architectures
- Understand how we got here – the milestones marking the maturity of Kong
- Gain visibility into the future of APIs and the implications for your architecture – Cloud-Native First, but hybrid while you get there.
- Why you need a solution that can support all of your deployment patterns.

In a short period of time, service APIs went from being primarily an edge interface connecting developers outside of the organization with internal systems to the glue that binds those internal systems (microservices) into a functioning whole. Consequently, one of the unavoidable results of microservice-oriented architectures is that internal communication within the data center will increase. Service mesh arose as a potential solution to the challenges that arise from increased East-West traffic by providing a different framework for deploying existing technology.

However, most of what service mesh introduces has been provided for many years by API Management products. Features such as observability, network error handling, health-checks, etc. are hallmarks of API management. These features don’t constitute anything novel in themselves, but as a pattern, service mesh introduces a new way of deploying those features within our architecture.

Join Kong CTO and Co-Founder Marco Palladino as he walks attendees through the architectural changes that have led to the rise of service mesh and why legacy API management solutions born before the advent of containers can’t keep up.

Webinar takeaways:

- Service mesh as an architecture pattern, not a technology
- The implications of adopting microservices-oriented architectures
- Why traditional API management solutions can’t keep up

Transitioning to a microservices architecture?

As microservices become an evermore mission-critical component of your enterprise architecture, there are a few challenges that will become increasingly salient. The need for scalability, high performance, and flexibility will make you think about APIs differently.

In this webinar, Aaron Miller and Cooper Marcus discuss the peculiar challenges of microservices architectures. They also demonstrate how Kong meets these challenges by being lightweight, super fast, and infrastructure agnostic.