The latest update of Kong (0.6.0) is a big one, and ships with some important improvements and breaking changes. Before upgrading please carefully follow the recommended Upgrade Guide.
Clustering is the most important new feature, which dramatically improves the performance of Kong and represents one of the building blocks that future features and plugins will be built upon.
Unlike previous Kong version, Kong >= 0.6.0 nodes pointing to the same datastore must join together to form a Kong Cluster. Kong automates joining and leaving nodes from a cluster, given that the right configuration is being provided.
To learn more about clustering please take a look at the Clustering Reference.
Performance & Uptime improvements
Compared to the previous 0.5.x, this new version of Kong ships with an improved and more predictable performance, by being able to handle more requests, with a lower response time and error rate (Y: req/s for reply rate, ms for full roundtrip response time, % for error rate – X: number of req/s):
This performance improvement has been achieved by upgrading the in-memory cache invalidation strategy, which now leverages cluster-wide invalidation events that are being triggered only when the data is being updated in the datastore.
By relying less on the datastore, it also means that Kong better tolerates database downtimes, improving the overall uptime of the system.
You can learn more about this benchmark here.
- More logging options, with the new Loggly, Datadog and Syslog plugins.
- Many Cassandra improvements, including properly recognizing a Cassandra cluster.
- Fixes the concurrent ID and token generation problem that was affecting the previous versions.
- New CLI commands: “kong cluster” and “kong status”.
- Improves Admin API in various areas, including a new “/cluster” endpoint and an improved “/status” endpoint.
- Introduces a new configuration format in “kong.yml”.
- And much more.
To update to the latest version, simply follow the installation instructions.
Upgrading from older versions
If you are upgrading from an older version of Kong < 0.6.0, then follow the upgrade instructions in order to make your Kong cluster functioning after updating to 0.6.0.
We are looking forward to seeing you at our Kong Meetup in San Francisco, on January 28th.