The latest from the Apiman Blog
The Apiman blog presents the latest Apiman release news and insights. We also share relevant API and software engineering content that we think you will find interesting.
Version 1.3.5.Final of Apiman is released
Apiman 1.3.5.Final is out and ready for you all to try.
This just contains some UI reversions, as we still have some tough-to-fix gremlins. We’ll bring the updates back once we’re able to fix the issues.
It contains all the same fixes and features as 1.3.4.Final.
Version 1.3.4.Final of Apiman is released!
Apiman 1.3.4.Final is out and ready for you all to try.
You may be wondering where 1.3.2.Final and 1.3.3.Final are; early community testing found some regressions, so we skipped formally announcing those.
Version 1.3.1.Final of apiman is released!
Version 1.3.0.Final of apiman is released!
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 ground for the upcoming initial community integration with 3scale, as outlined in previous blogs.
Performance tuning the Apiman Gateway (WildFly, EAP, Tomcat)
In this blog, we’ll outline a few simple tweaks you can make to improve the performance of the Apiman Gateway when running on servlet platforms (WildFly, EAP, Tomcat, etc).
Most of the focus will be on WildFly and EAP, but others will be more broadly applicable.
Naturally, these are very rough pointers and should merely be hints for areas that could prove fruitful. There’s no one-size-fits all approach to tuning, so always profile and keep tweaking to find the best settings for your workloads.
3scale and apiman - Part Deux
It’s been almost two months since Red Hat announced it was acquiring 3scale Technologies and turning the 3scale API Management solution into a Red Hat supported product. In that time, we’ve been trying to figure out some stuff for the apiman community. Here some of the things we wanted to suss out:
How the apiman development team can best focus its efforts, now that 3scale will be the basis for Red Hat’s API Management technology.
How to best support the existing apiman community going forward, given the restrictions on continued development of the apiman API Management solution.
How can existing apiman users transition to a Red Hat supported API Management solution.
It doesn’t sound like much, but it actually really is. We’ve made some preliminary decisions, and because we want to be as transparent and upfront as possible, read on to find out what they are!
Red Hat, 3scale, and apiman?
Because the apiman project is sponsored primarily by Red Hat, you may be wondering how this impacts the project and its open source community. In today’s blog post, I’ll do my best to answer that question as honestly and transparently as I can.
Version 1.2.4.Final of apiman is released!
Greetings, earthlings! On Friday of last week we released the absolute best version of apiman ever! This release has a fair number of bugs fixed, as well as a few new things. Read on for the details!
Covering Your Assets: Data Encryption in API Management
In a world where APIs are quickly becoming the standard, most of us understand the importance of following best practices for API security. We authenticate, authorize and throttle requests. We encrypt the data that we share with other applications (hopefully!). But we often neglect one of the most essential components of the API layer: data storage.
Using apiman in a network with limited Internet access
In plenty of enterprises, networks are either locked down or have very limited access to the Internet; often for security, privacy or other practical reasons.
We’ve carefully designed apiman to be fully featured and easily configured when no Internet access is available; providing a great deal of flexibility and eschewing any "off-site only" functionality.
So, if you’re looking for API management in a locked-down network or Internet-free environment, read on!
Apiman 1.2 - Introduction to User Roles in apiman
In this post, we’ll examine apiman user roles. In the apiman data model, all data elements exist in the context of the organization. The same holds true for user memberships as users can be members of multiple organizations. Permissions in apiman are role based. The actions that a user is able to perform are dependent on the roles to which the user is assigned when a user is added as a member of an organization.
Version 1.2.3.Final of apiman is released!
Greetings, earthlings! Yesterday we released the best version of apiman yet, and I’m not just saying that because the version number (1.2.3.Final) is awesome. This release has a bunch of bug fixes in it, as well as a few targeted new features. Read on for more details!