Having worked with many customers and prospects at Kong, one of the main requirements we often hear is how to handle dynamic routing based on the URL and headers. In this blog post, I will cover different use cases we come across for dynamic routing and how Kong can address them. The default behavior of an API gateway is to route the incoming request to the appropriate upstream service. If you are new to Kong, a Service object represents the upstream API or Service.

Welcome to another one of our Community Roundups, folks! Looks like summer really kicked in with all the heat, so we thought we’d bring you some refreshments in the form of some tweets and articles. Let’s see what we have this time!

Kubernetes (k8s) enables you to efficiently orchestrate container management, in the cloud or on-premises. As a whole, k8s provides many benefits, including features for self-healing, automated rollouts and rollbacks, load distribution, and scalability. However, k8s is a highly complex platform and requires extensive configuration.

In a global economy, real-time data analysis is closely related to business success. Without data-driven insights, organizations find it challenging to remain competitive, improve company performance, and deliver strong user experiences, regardless of their industry. To match the pace of business, companies require transparent, data-driven relationships.

k6 v0.27.0 is finally out! It has been over a year since the k6 team started working on this release, which includes a multitude of new features, improvements, bugfixes and beyond. This release was an effort to redefine performance and load-testing in k6, by introducing a new execution engine and lots of new executors on top, along with the most requested feature, scenarios. It also includes many UX improvements and bugfixes.

We are happy to announce the general availability of Kuma 0.7! This is very big release that includes countless improvements and updates, specifically when it comes to multi-zone deployments configuration and Kubernetes deployments. We strongly suggest to upgrade to this new version while paying attention to a few breaking changes that 0.7 introduces. For a complete list of features and updates, take a look at the full changelog.

Hans Ulrich Obrist once said that “everything I do is somehow connected to velocity”. We couldn’t agree more. As is in most companies, there’s always something affecting your team’s velocity, whether that’s a new work from home routine, a change in budget, or a variety of other reasons. So many influences are out of your control- how do you make sure that your devs are working at optimal velocity?

Healthcare organizations like yours are riddled with mountains of data and document streams coming in each day. Whether it’s patient records, claims, denials, remits, or clinician credentials… the list goes on. All these items can quickly create chaos and confusion without proper organization protocols in place to handle this data deluge. When employees are tasked with manually handling inbound document management, there is the potential for a wide array of complications, including.

Medical devices have become increasingly complex as technology evolves, and the sheer number of these devices now being worn or implanted has grown exponentially over the past few years. There are currently over 500,000 different types of smart, connected medical devices in use that have the ability to collect, share, or store private patient data and protected health information (PHI)(1).

Coronavirus has impacted the travel industry, but as it adapts, there is one factor airlines have always worked hard to minimize: delayed flights. Arriving late or missing a connection can severely impact the customer experience, which is why airlines work hard to maintain high rates of on-time performance (OTP). To that end, pilots may have to use extra fuel to make up for a delayed departure or to reach a destination early, even if it means circling the airport before landing.