All around the world – API Workshops for OAuth, Mobile, REST
Here at Axway, we regularly run API Workshops worldwide which bring together API practitioners in discussion, debate, and exposure to technologies such as OAuth 2.0, API developer portal design, and identity. And when we say “worldwide”, we mean worldwide. To illustrate this, my colleague Philipp Schöne has created an interactive map on CartoDB of the API Workshops over the past year, with photos of each. All that’s missing is a backing track of Daft Punk’s “Around the World” :)

Each API Workshop has been eventful in its own way, and for example I recall the spirited debate on SOA and API Management, led by Kevin Kohut from Accenture and Randy Heffner from Forrester, at our API Workshop in Phoenix in September.

Here are other highlights I’d pick out:

(This post appears in slightly different form at soatothecloud.com.)

Is your MFT ready for the IBM z13?

IBM recently announced the availability of a “new” mainframe dubbed the z13. Flying in the face of the “mainframe is dead” mantra, IBM is introducing a mainframe that is poised to address the needs of mobile, analytics (big data), cloud, and security. According to IBM, it can handle 2.5 billion transactions a day. It’s a bit more impressive when it’s written out fully: 2,500,000,000 transactions a day. This represents the total number of transactions of 100 cyber-malls … for every day of the year!

It’s clear that IBM sees value in what many pundits deem as legacy technology. In fact, they’re stating, by this introduction, that legacy infrastructure can (and should) be updated and invested in. “Legacy” technology is often the heart of a business that cannot be ripped and replaced. It can be “upgraded,” as IBM is showing here. In fact, they’re acknowledging that there are concerns with legacy technology (i.e., the focus on security: real-time encryption of data) which have to be addressed, in addition to adding new functionality.

So the mainframe is being updated — what does this mean for other infrastructure? Well, I’d argue that it means that everything that is considered legacy should be open to updating. Just because it was working (mainframes worked) doesn’t mean that it meets the needs of the current business environment needs around security, visibility, and integration.

This brings us to Managed File Transfer technology. It’s often considered legacy. It’s often believed it should be left in place “because it does the job.” Whether your file transfer technology is some version of SFTP or a purpose-built MFT solution, the introduction of the z13 should cause people to take the time to reevaluate their legacy technology.

We at Axway recommend that you review your legacy technology, including your MFT technology, and ask the question, “Is my MFT ready for the z13?”