At Kong, our mission is to deliver the best API lifecycle management experience for the cloud native era. Driven by our dedication to meeting the dynamic demands of modern end-to-end API management, we’ve introduced an array of new Kong Konnect features in April, enhancing functionality and elevating the user experience.
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.
Agile teams must adapt to changing requirements and continuously ship new features. But, while automated tests are faster, they take time to set up and still need ongoing maintenance. So, how do you decide when to invest time and energy in test automation and when to use manual tests? Striking the right balance is critical to success.
Many organizations are experiencing a digital transformation to keep pace with the rapidly changing technology landscape and the increasing demand for faster time-to-market. By embracing Agile principles, like collaboration, iterative development, and continuous feedback, you can respond more quickly to changing requirements and market conditions. But these transitions don’t happen overnight.
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.
