Welcome!

Microservices Expo Authors: Elizabeth White, Roger Strukhoff, Pat Romanski, Dana Gardner, Ruxit Blog

Related Topics: @ThingsExpo, Microservices Expo, @CloudExpo, @BigDataExpo

@ThingsExpo: Blog Feed Post

Rise of the Thing - Internet of Things

The Internet of Things (IoT) is giving rise to a whole new set of protocols for API access

Here are some predictions for the API space for 2014:

Rise of the Client
It's generally agreed that an API is only as good as the clients which use it. An unused API is a failure. So that's why it's odd that so much attention has focused on the server side of APIs, with comparatively little attention paid to the client side (there are exceptions though, like Runscope's handy Request Editor and hurl.it, to help developer API clients).

If you ask an API provider about how their API is going to be called by clients, often you are met with a hand-wavy answer along the lines of "It's REST, so it's easy". While it may be true that it's easy to hack together a client to call the API that "just works", the problem is that that's all it does. It "just works", but doesn't provide the high-level benefits such as:
- Ensuring the API is responding according to your expected service level
- A broker layer so that you're not locked into any particular API provider, or:
- API orchestration

At Axway we've seen that our API Gateway is frequently used at the Client Side, adding a layer of visibility and control to API usage from the client's point of view, as well as providing an independent audit log of API usage, separate from the logs provided by the API provider. All of this points to the rise of the client.

Another major factor involving the rise of the important of the API client is raft of new protocols associated with Machine-to-Machine API access, used in smart-meter or "connected car" environments for example. Which leads us nicely on to the next prediction...

Rise of the Thing
(hat-tip to Zahid Ghadialy from EE for this title, taken from his excellent recent presentation)

The Internet of Things (IoT) is giving rise to a whole new set of protocols for API access. Until recently, it was taken for granted that JSON is all-conquering and predominant. In my view, the popularly of JSON for APIs is as much to do with the widespread usage of dynamic languages on the client side (JavaScript in particular, of course) as it is to do with the smaller size of JSON relative to XML.

In the word of IoT, with embedded devices on the client and greater bandwidth constraints, it's not the case that clients will always be JavaScript based and expecting JSON. In IoT, we see MQTT, CoAP, and AMQP. All different, but all existing to deal with the low-latency and message size constraints of IoT devices. In this case, it isn't possible to simply throw together a REST client with JavaScript on the client - the result would be hopelessly inefficient since even JSON is too verbose. Ironically, with the IoT standards we are back to binary encoding, something I wrote about (BER encoding for XML) way back in 2002.

I would also watch Google's Protocol Buffer, which with protobuf.js provides JavaScript without the JSON size overhead.

Going Meta
In the world of SOA, we saw that each Web Service could be associated with metadata expressed using WS-PolicyAttachment with WSDL. The mention of any WS-* specification is enough to make anyone cringe, but in the case of SOA, at least there were standards for attaching meta-data to services.

In the case of APIs, we have sites such as ProgrammableWeb which provide human-readable information about APIs. But this is not the same as machine-readable information which a client can consume, conveying information how to call the API, security tokens (e.g. OAuth 2.0 Access Token) required, and expected response times.

Ole Lensmar wrote a great round-up of the API metadata options, back in the summer (now you would add RAML to this list). For Enterprise APIs, with security and quality-of-service requirements, I expect API metadata to grow in importance in 2014.

Traditional and API-based Integration continue to converge
Axway got a jump on this trend back in late 2012, with the acquisition of Vordel. In fact, at the time of the Vordel acquisition, Kin Lane foretold that "I predict in 2013-2015 we are going to see more of these types of acquisitions occurring. Large software companies are going to need a robust set of API tools to bring legacy systems into the modern, API driven economy." And how right he was! 2013 saw a slew of further acquisitions. I would hope that my predictions could be as accurate as Kin's.

There is clearly a need to take advantage of API-based integration, but in tandem with more traditional integration technologies. It's not a case of "either/or". Here at Axway, with API-based integration incorporated into our portfolio, we provide customers with a single suite solution covering B2B, APIs, managed file transfer, and even email security. In 2014, APIs will not be an isolated "new new thing", but will be working in tandem with traditional integration technologies.

SOA and APIs no longer adversarial
Paolo Malinverno from Gartner likes to say that "When people talk about APIs and Services, 99% of the time they are talking about the same thing". One of the big take-aways of the recent Gartner AADI conference was that we've gotten over the adversarial talk of "SOA versus APIs" and now there is a realization that they are linked. The linkage goes both ways. For example, APIs can be built on SOA principles (loosely-coupled, abstracting underlying implementation details), and SOA architecture itself can be used to manage APIs. Ideas from SOA, such as management of service meta-data in a repository, find new life in API Management with customizable API Catalogs in API Developer Portals.

In 2014, I expect to see more healthy realization that SOA principles are complimentary to API Management,

More API Breaches
Finally, on a less positive note, I believe we will see more successful attacks on APIs. In 2013 we had the attack on Buffer's API and, just last week, the attack on Snapchat's API. Earlier in the year we saw DoS attacks on banking websites which also brought down Web APIs (resulting in some banking mobile apps becoming unusable). One of the key things which API Gateways do is to protect APIs from attack. Of course, they also provide more positive advantages like API Quota Management, caching, and REST-SOAP transformation. But, with growing awareness of API breaches, the security factor will grow in 2014.

Happy 2014 everyone!

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.

@MicroservicesExpo Stories
Using new techniques of information modeling, indexing, and processing, new cloud-based systems can support cloud-based workloads previously not possible for high-throughput insurance, banking, and case-based applications. In his session at 18th Cloud Expo, John Newton, CTO, Founder and Chairman of Alfresco, described how to scale cloud-based content management repositories to store, manage, and retrieve billions of documents and related information with fast and linear scalability. He addres...
Cloud Expo 2016 New York at the Javits Center New York was characterized by increased attendance and a new focus on operations. These were both encouraging signs for all involved in Cloud Computing and all that it touches. As Conference Chair, I work with the Cloud Expo team to structure three keynotes, numerous general sessions, and more than 150 breakout sessions along 10 tracks. Our job is to balance the state of enterprise IT today with the trends that will be commonplace tomorrow. Mobile...
Akana has announced the availability of version 8 of its API Management solution. The Akana Platform provides an end-to-end API Management solution for designing, implementing, securing, managing, monitoring, and publishing APIs. It is available as a SaaS platform, on-premises, and as a hybrid deployment. Version 8 introduces a lot of new functionality, all aimed at offering customers the richest API Management capabilities in a way that is easier than ever for API and app developers to use.
SYS-CON Events announced today that Isomorphic Software will exhibit at DevOps Summit at 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Isomorphic Software provides the SmartClient HTML5/AJAX platform, the most advanced technology for building rich, cutting-edge enterprise web applications for desktop and mobile. SmartClient combines the productivity and performance of traditional desktop software with the simp...
DevOps at Cloud Expo, taking place Nov 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with 19th Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to wait for long dev...
SYS-CON Events announced today that 910Telecom will exhibit at the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Housed in the classic Denver Gas & Electric Building, 910 15th St., 910Telecom is a carrier-neutral telecom hotel located in the heart of Denver. Adjacent to CenturyLink, AT&T, and Denver Main, 910Telecom offers connectivity to all major carriers, Internet service providers, Internet backbones and ...
The burgeoning trends around DevOps are translating into new types of IT infrastructure that both developers and operators can take advantage of. The next BriefingsDirect Voice of the Customer thought leadership discussion focuses on the burgeoning trends around DevOps and how that’s translating into new types of IT infrastructure that both developers and operators can take advantage of.
With so much going on in this space you could be forgiven for thinking you were always working with yesterday’s technologies. So much change, so quickly. What do you do if you have to build a solution from the ground up that is expected to live in the field for at least 5-10 years? This is the challenge we faced when we looked to refresh our existing 10-year-old custom hardware stack to measure the fullness of trash cans and compactors.
This digest provides an overview of good resources that are well worth reading. We’ll be updating this page as new content becomes available, so I suggest you bookmark it. Also, expect more digests to come on different topics that make all of our IT-hearts go boom!
The emerging Internet of Everything creates tremendous new opportunities for customer engagement and business model innovation. However, enterprises must overcome a number of critical challenges to bring these new solutions to market. In his session at @ThingsExpo, Michael Martin, CTO/CIO at nfrastructure, outlined these key challenges and recommended approaches for overcoming them to achieve speed and agility in the design, development and implementation of Internet of Everything solutions wi...
19th Cloud Expo, taking place November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud strategy. Meanwhile, 94% of enterpri...
Sharding has become a popular means of achieving scalability in application architectures in which read/write data separation is not only possible, but desirable to achieve new heights of concurrency. The premise is that by splitting up read and write duties, it is possible to get better overall performance at the cost of a slight delay in consistency. That is, it takes a bit of time to replicate changes initiated by a "write" to the read-only master database. It's eventually consistent, and it'...
To leverage Continuous Delivery, enterprises must consider impacts that span functional silos, as well as applications that touch older, slower moving components. Managing the many dependencies can cause slowdowns. See how to achieve continuous delivery in the enterprise.
Node.js and io.js are increasingly being used to run JavaScript on the server side for many types of applications, such as websites, real-time messaging and controllers for small devices with limited resources. For DevOps it is crucial to monitor the whole application stack and Node.js is rapidly becoming an important part of the stack in many organizations. Sematext has historically had a strong support for monitoring big data applications such as Elastic (aka Elasticsearch), Cassandra, Solr, S...
Thomas Bitman of Gartner wrote a blog post last year about why OpenStack projects fail. In that article, he outlined three particular metrics which together cause 60% of OpenStack projects to fall short of expectations: Wrong people (31% of failures): a successful cloud needs commitment both from the operations team as well as from "anchor" tenants. Wrong processes (19% of failures): a successful cloud automates across silos in the software development lifecycle, not just within silos.
There's a lot of things we do to improve the performance of web and mobile applications. We use caching. We use compression. We offload security (SSL and TLS) to a proxy with greater compute capacity. We apply image optimization and minification to content. We do all that because performance is king. Failure to perform can be, for many businesses, equivalent to an outage with increased abandonment rates and angry customers taking to the Internet to express their extreme displeasure.
Right off the bat, Newman advises that we should "think of microservices as a specific approach for SOA in the same way that XP or Scrum are specific approaches for Agile Software development". These analogies are very interesting because my expectation was that microservices is a pattern. So I might infer that microservices is a set of process techniques as opposed to an architectural approach. Yet in the book, Newman clearly includes some elements of concept model and architecture as well as p...
A company’s collection of online systems is like a delicate ecosystem – all components must integrate with and complement each other, and one single malfunction in any of them can bring the entire system to a screeching halt. That’s why, when monitoring and analyzing the health of your online systems, you need a broad arsenal of different tools for your different needs. In addition to a wide-angle lens that provides a snapshot of the overall health of your system, you must also have precise, ...
SYS-CON Events announced today that Venafi, the Immune System for the Internet™ and the leading provider of Next Generation Trust Protection, will exhibit at @DevOpsSummit at 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Venafi is the Immune System for the Internet™ that protects the foundation of all cybersecurity – cryptographic keys and digital certificates – so they can’t be misused by bad guys in attacks...
Monitoring of Docker environments is challenging. Why? Because each container typically runs a single process, has its own environment, utilizes virtual networks, or has various methods of managing storage. Traditional monitoring solutions take metrics from each server and applications they run. These servers and applications running on them are typically very static, with very long uptimes. Docker deployments are different: a set of containers may run many applications, all sharing the resource...