KrakenD servers with telemetry enabled help us to understand the usage of KrakenD in production. Last month we witnessed 356K running instances, and we wanted to share some data with you. 👇 From mid-March, we have seen an exciting increase in the number of KrakenD instances seen per day: x12! The trend is just beautiful, including the cumulative. According to our internal definition, an instance is every time a KrakenD is started.
The KrakenD team is pleased to announce the release of KrakenD 1.1. You can get it packaged from the download page. Some of the highlights include: Kafka integration Extended Docker image Added Telemetry for Azure Monitor More performance improvements Kafka integration From now on, users of Apache Kafka can publish and subscribe from KrakenD. The Kafka integration saves you from writing application logic to interact with the streaming platform and let the gateway be an active player in the event architecture pattern.
In November 2016, we released KrakenD framework to the public. Today, after three years serving traffic around the world, and a lot of lessons learned on the way, KrakenD 1.0 is out 🎉🎉🎉 KrakenD 1.0 is our announcement to the world that our libraries are now fully established and with the solid commitment of keeping backward compatibility. In the last twelve months, we have seen 120,000+ clusters in the world and 1M+ docker pulls, but as we always did (since 0.
The gRPC protocol is becoming trendy in the era of microservices. Its compactness and backward-compatibility make it very attractive. However, it requires custom code to work with it. In this article, we’ll show you how to get all the benefits from the gRPC protocol and the gRPC-gateway without coding any business logic to use your gRPC services as regular backends. Moreover, avoiding the extra network hop!
Starting your krakend.json configuration from scratch and writing every attribute in a blank editor might be a difficult and time consuming task, and that’s why we have the KrakenDesigner. KrakenDesigner is an aid tool to generate KrakenD configurations for the uninitiated audience. It produces a verbose output of the configuration file and explicitly writes unneeded attributes to let you see that a specific configuration option exists. These attributes I am mentioning are not necessary because they contain default values and the server is not going to alter its behavior.
It’s been only one month since we released KrakenD 0.8, and although we have been releasing new versions approximately every 3 months, we have very interesting features that can’t wait! KrakenD 0.9 comes with a series of very demanded features. Let’s get started! Integration with AMQP The AMQP integration allows you to send and receive messages to and from a queue through the KrakenD API Gateway. This feature enables the gateway to become in both a subscriber and a consumer of messages for asynchronous processing and opens the doors to very different implementations we were seeing.
KrakenD 0.8 is a significant release as it brings numerous code changes and functionality. The framework brings +100 commits, the gateway +50 commits and even more changes in the components. A lot of refactoring and component updates has taken place. The big picture is a move from a single binary application to become a package with several internal binaries. See the details below. KrakenD framework The KrakenD framework brings +100 commits compared to 0.
KrakenD is an API Gateway written in Go that uses a single configuration file to define its whole behavior. As the configuration file might be complicated, the KrakenDesigner is a javascript-based user interface to edit this file, and we were missing the capability of reproducing directly on javascript the existing gateway pipes so that users could run manual tests over the editing configuration. In this post, we are going to explain how we included KrakenD framework components in a .
The most relevant features for the 0.7 release are increased metrics and tracing options, and functionality that has been requested by many, the sequential proxy merger. During this release, we also updated the KrakenD brand with a new logo, and we added more documentation. On the metrics side, we can now send structured events using GELF to your Graylog Cluster. Opencensus middleware adds new functionality to push metrics to your Google StackDriver account.
The 0.6.1 release adds TLS and enables HTTP2 and HTTPS. TL;DR This release brings HTTP2 and HTTPS to KrakenD. It also upgrades Go from 1.10 to 1.11 and fixes forwarded query string parameters to backends that are using arrays and repeated variables. The KrakenDesigner (UI) is also updated to reflect these changes. KrakenD framework The KrakenD framework has the following relevant changes: NEW: Added support for HTTP2/HTTPS FIX: query string parameters works now with arrays and repeated variables (e.
We use cookies to understand how you use our site and to improve your overall experience. By continuing to use our site, you accept our Privacy Policy. More information