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.
API testing has many moving parts, and in this post you'll be presented with the 5 most essential tools and methodologies.
As an API provider, you probably picture bringing in some type of revenue as part of your API business model. When you first begin the journey of monetizing your API product, you’ll likely find that the complexities of monetization run deep. Much of the time, solving this problem extends beyond the capabilities of a typical API gateway or API management platform.
