We’re excited to announce the release of Kong Mesh and Kuma 2.2. This new minor release adds some long-awaited enterprise features, more incremental improvements to our UI and policies, and many more minor features and bug fixes. In order to take advantage of the latest and greatest in service mesh, we strongly suggest upgrading to Kong Mesh 2.2. Upgrading is easy through kumactl or Helm.

At first glance, that does not make sense, right? The title suggests you should invest your DevOps/Platform team’s time in introducing a new product that most likely will: Through this article, we’ll show you that even though those initial concerns are justified, the overall benefits that can be realized by adopting a service mesh can outweigh any initial effort and investments.

As the world’s most popular API Gateway, Kong Gateway is flexible and can be adapted to various environments and deployment configurations. This flexibility means some time should be taken to make good architectural decisions for the use cases in mind. For example, the best configuration for a developer’s workstation isn’t the ideal one for a high SLA deployment. Fitness for purpose is therefore the objective.

The ability to rapidly assemble and reassemble APIs and microservices has become a competitive differentiator across all industries — allowing organizations to pivot business models and deliver amazing customer experiences at speed and scale. Innovative organizations are pushing to become agile and transforming by adopting cloud native technologies that allow them to build more resilient software quickly that easily scales.