Dustup at OSCON – Missing the API Bigger Picture?

Fellow Cloud pontificator Randy Bias caused quite a stir at O’Reilly’s Open Source Convention (OSCON) this week. Basically, he suggested that the OpenStack crowd capitulate to Amazon Web Services (AWS). Instead of building competing APIs, Randy opined, OpenStack should follow in Eucalyptus’s footsteps and simply comply with the AWS de facto API standards.

His reasoning: AWS has already sown up the Public Cloud marketplace. No sense for OpenStack to keep beating their collective heads against that wall. Instead, OpenStack should go after the Private Cloud space. Because APIs are central to the Hybrid Cloud story, being able to connect OpenStack Private Clouds to AWS or other AWS-compatible Clouds is where the money is.

OpenStack-based Public Cloud providers like Rackspace are sure to disagree, but I think Bias is on to something. AWS clearly dominates public IaaS. Hybrid Clouds are unquestionably where the money is, for any consultant or service provider serving the enterprise market. I would also go so far as to say that OpenStack is well behind AWS, and losing ground – so playing a “can’t beat ‘em so join ‘em” game makes sense.

Fair enough, but I think there’s a larger, more strategic issue here that both sides of the Cloud API discussion appear to be missing. We’ve outgrown the old notion of API as a tightly coupled, procedural interface. We’ve been through the fire of Web Services as we struggled to achieve loose coupling with contracted interfaces. And now we’ve come out on the other side, calling our software interfaces APIs once more. But have we learned anything?

What we really want from our software interfaces is deep interoperability. We want them to abstract the underlying software capabilities, not only to support different implementations at the same time, but also to support changing implementations over time. Web Services took us part way there, but they needed intermediaries to abstract multiple implementations and rigorous repository-based governance to handle versioning.

Hypermedia-Oriented Architecture (HOA), the architectural style that REST was meant to be, takes us further. Hypermedia take care of interface discoverability, helping to resolve the agility issues that plague typical APIs.

True, HOA needs work. There are still missing pieces to the deep interoperability puzzle. But as the OSCON API dustup indicates, people aren’t even thinking about hypermedia-driven discoverability when they’re thinking about APIs. Stop chopping down trees, folks, there’s a whole forest out there to figure out!

Share the Post:
Share on facebook
Share on twitter
Share on linkedin


The Latest

homes in the real estate industry

Exploring the Latest Tech Trends Impacting the Real Estate Industry

The real estate industry is changing thanks to the newest technological advancements. These new developments — from blockchain and AI to virtual reality and 3D printing — are poised to change how we buy and sell homes. Real estate brokers, buyers, sellers, wholesale real estate professionals, fix and flippers, and beyond may

man on floor with data

DevX Quick Guide to Data Ingestion

One of the biggest trends of the 21st century is the massive surge in internet usage. With major innovations such as smart technology, social media, and online shopping sites, the internet has become an essential part of everyday life for a large portion of the population. Due to this internet

payment via phone

7 Ways Technology Has Changed Traditional Payments

In today’s digital world, technology has changed how we make payments. From contactless cards to mobile wallets, it’s now easier to pay for goods and services without carrying cash or using a checkbook. This article will look at seven of the most significant ways technology has transformed traditional payment methods.