SDN Journal Authors: Liz McMillan, Pat Romanski, Elizabeth White, Yeshim Deniz, TJ Randall

Related Topics: Microservices Expo, @CloudExpo, @DXWorldExpo, SDN Journal, @ThingsExpo, @DevOpsSummit

Microservices Expo: Blog Feed Post

APIs: What Will Happen With The Internet of Things?

It is true that Internet of Things is bringing in a broader meaning of 'APIs' to go beyond 'the same technology as websites'

Until recently, when I would talk about "APIs", I would qualify it by saying "Web APIs", in order to distinguish from the older meaning of APIs as more the tightly-coupled APIs used in Java, C/C++, or even Visual Basic. If you just said "APIs", until recently, some people may think you mean APIs like the Windows API (I can remember Charles Petzold's excellent Windows API book was on my desk back when I was a programmer at an EDI VAN in the 90s).

Recently Kin Lane has posted some good questions about the nature of APIs on his blog - he begins by explaining:

Just exactly what an API is, is always up for debate. APIs have been around since before the Internet. API Evangelist focuses in on what I call web APIs, that were built using the same technology as websites, and were made even popular for delivering valuable data and resources to mobile phones.

Notice "Web APIs" also. But, Kin explains that technology may be moving on. Recently, I have seen APIs move on from just "Web APIs". This is for two reasons. Firstly, people know that "APIs" means the modern meaning of the term, so there is less need to qualify what you mean. But secondly, and more fundamentally, there is now a realization that APIs refers in the broad sense to how businesses enable new channels, using technology links to devices, partners, and the market in general.

Kin goes on to ask

" What will happen with the Internet of Things? Will there be APIs that are tailored for home automation devices or just our cars?"

It is true that Internet of Things is bringing in a broader meaning of "APIs" to go beyond "the same technology as websites", and towards more tailored protocols and data formats (even JSON is too verbose in many Internet of Things scenarios).

Here at Axway, we see that customers see their API as encompassing not only HTTP+JSON style Web APIs, but also including their B2B interfaces, so it's "API in a broad sense". A business may use a variety of protocols, including EDI, ebXML, and Managed File Transfer as part of its overall "API". An "API" is now you can automate business across the firewall, not limited to a particular set of technologies. Just like with SOA, it's important to disassociate the architecture from the enabling technology. I think this is a very useful debate kicked off by Kin Lane, and it chimes very well with what we're seeing at Axway in the B2B and Internet of Things markets.

More Stories By Mark O'Neill

Mark O'Neill is VP Innovation at Axway - API and Identity. Previously he was CTO and co-founder at Vordel, which was acquired by Axway. A regular speaker at industry conferences and a contributor to SOA World Magazine and Cloud Computing Journal, Mark holds a degree in mathematics and psychology from Trinity College Dublin and graduate qualifications in neural network programming from Oxford University.

CloudEXPO Stories
With more than 30 Kubernetes solutions in the marketplace, it's tempting to think Kubernetes and the vendor ecosystem has solved the problem of operationalizing containers at scale or of automatically managing the elasticity of the underlying infrastructure that these solutions need to be truly scalable. Far from it. There are at least six major pain points that companies experience when they try to deploy and run Kubernetes in their complex environments. In this presentation, the speaker will detail these pain points and explain how cloud can address them.
The deluge of IoT sensor data collected from connected devices and the powerful AI required to make that data actionable are giving rise to a hybrid ecosystem in which cloud, on-prem and edge processes become interweaved. Attendees will learn how emerging composable infrastructure solutions deliver the adaptive architecture needed to manage this new data reality. Machine learning algorithms can better anticipate data storms and automate resources to support surges, including fully scalable GPU-centric compute for the most data-intensive applications. Hyperconverged systems already in place can be revitalized with vendor-agnostic, PCIe-deployed, disaggregated approach to composable, maximizing the value of previous investments.
When building large, cloud-based applications that operate at a high scale, it's important to maintain a high availability and resilience to failures. In order to do that, you must be tolerant of failures, even in light of failures in other areas of your application. "Fly two mistakes high" is an old adage in the radio control airplane hobby. It means, fly high enough so that if you make a mistake, you can continue flying with room to still make mistakes. In his session at 18th Cloud Expo, Lee Atchison, Principal Cloud Architect and Advocate at New Relic, discussed how this same philosophy can be applied to highly scaled applications, and can dramatically increase your resilience to failure.
Machine learning has taken residence at our cities' cores and now we can finally have "smart cities." Cities are a collection of buildings made to provide the structure and safety necessary for people to function, create and survive. Buildings are a pool of ever-changing performance data from large automated systems such as heating and cooling to the people that live and work within them. Through machine learning, buildings can optimize performance, reduce costs, and improve occupant comfort by sharing information within the building and with outside city infrastructure via real time shared cloud capabilities.
As Cybric's Chief Technology Officer, Mike D. Kail is responsible for the strategic vision and technical direction of the platform. Prior to founding Cybric, Mike was Yahoo's CIO and SVP of Infrastructure, where he led the IT and Data Center functions for the company. He has more than 24 years of IT Operations experience with a focus on highly-scalable architectures.