We are happy to announce the release of Kuma 1.0.1 with a few improvements and fixes, and we suggest to upgrade to start using the greatest and latest. This is a minor update on top of Kuma 1.0 that shipped last week with over 70+ features and improvements. For a complete list of features and updates, take a look at the full changelog. Join us on our community channels to learn more about Kuma, including our official Slack chat.
In this guide you’ll learn how to send Moesif behavioral emails with Mailgun. Moesif behavioral emails is a service that sends emails to customers based on their requests to your API. These emails can be used to notify users about technical issues, such as API limits or broken integrations, as well as business-related events such as how many items you’ve shipped. If something can be mapped to an API call, then you can send an email on it.
From the Kong API Gateway perspective, using Consul as its Service Discovery infrastructure is one of the most well-known and common integration use cases. With this powerful combination more flexible and advanced routing policies can be implemented to address Canary Releases, A/B testings, Blue-Green deployments, etc. totally abstracted from the Gateway standpoint without having to deal with lookup procedures.
We are in the midst of an explosion of APIs and microservices. For some, the first instinct of creating an API is to get down to building one. Some level of planning will help manage the quality of APIs when working within a team. In this series of blogs, we will be sharing some guidelines on service design while working on API projects with Kong. Let us start by focusing on how to go about designing APIs that end up as entities that the Kong API Gateway runtime understands.
API Observability is a key component to properly execute APIOps Cycles and ensure your building something of value for your API users. If you’re not familiar with APIOps Cycles, take a look at this guide which provides an agile framework to quickly build APIs that are business-oriented and serve customer needs. API Observability itself is an evolution of traditional monitoring and born out of control systems theory.
Over the course of just a few years, the ways in which we consume content have changed dramatically. In order to compete in this new landscape and to adapt to the technological change that underpins it, media studios and other content producers should consider providing relatively open access to their proprietary content. This necessitates a cultural change across the industry.
