Red Hat
May 25, 2017
by marc@rhymewithgravy.com

Last week we released apiman 1.3.0.Final. It’s been rather a long while coming, but hopefully you’ll be pleased with the improvements.

This release has some important new features, a substantial number of bug-fixes, and marks the official release of the Apiman Vert.x Gateway.

Importantly, this release has a lot of background work which has prepared the the ground for the upcoming initial community integration with 3scale, as outlined in previous blogs.

Where can I find more information?

The release notes for this release can be found here:

And of course, all of the standard sources of information have been updated:

Highlights

Just want to know about the good stuff? Let’s have a brief look at some of the more important changes in this version.

Bug smashing galore

A substantial number of bugs have been resolved [1]. If there was something bugging you, then it’s worth trying out 1.3.0.Final to see whether your issue has been fixed.

Otherwise, please do consider filing an issue!

Vert.x comes to the fore

The Vert.x Apiman Gateway has finally left the tech preview stable and been reworked and polished to the point that it has been officially released. It is now the recommended platform for those who need high performance.

For those that aren’t familiar with Vert.x, it’s an asynchronous, reactive toolkit that provides a high throughput and low latency platform is perfectly matched to the apiman gateway.

Please try it out and let us know what you think! We hope you’ll be impressed.

Out of the box there are Elasticsearch and Headless configuration examples. It also uses an asynchronous log4j2 configuration which should provide excellent performance [2].

Here’s a really quick way to try it out.

  1. Download and run the WildFly 10 quickstart.

  2. Download and run the Vert.x Gateway distro.

  3. Add your new gateway through the Apiman UI.

  4. Start publishing stuff!

This is a gateway only implementation. It is paired with any Servlet-based Apiman Manager. Just add it through the Apiman UI.

Headless registry

Feeling headless? [3]. We’ve introduced an immutable headless registry that loads gateway configuration as JSON from a local or remote location (file, http or https).

It even supports authentication, if you need to secure that configuration.

At the moment it’s probably for more advanced users, as some JSON-wrangling is required, but it’s a really powerful feature that will suit many people’s immutable architectures. Some of users don’t actually need the apiman UI or Manager; as there is no human interaction aspects to their workflow (e.g. B2B scenarios, monitoring, managed through other systems, etc).

To find out more:

New documentation

Given the new additions, documentation has been reworked (excluding developer guide) and is now using GitBook. We welcome your critique on whether this is an improvement versus the older documentation and you can still figure out what you need.

Thank you!

There’s lots more good stuff to come and with much greater regularity, so stay tuned (releases, blogs, plugins, etc).

Thanks to the community members who have made contributions to this release via code, filing bugs, and even some in-person meetings.

Finally, it’s my pleasure to be doing my first release announcement for apiman, having stepped up to tech lead for the apiman gateway.


1 As usual, we probably forgot to create tickets for all of the bugs, so include "misc bugs splattered"
2 Usual caveats with logging apply.
3 Sorry.
Original Post