Last November, Gartner looked towards the future and predicted that in 2016, 6.4 billion connected things will be in use worldwide. Today is that future. Around us right now, billions of connected things are speaking to each other, passing data, and keeping our lives efficient and modern. From the things we wear (our smart watches, our fitness trackers), to the perks that make our lives easier (our navigation systems, our smart thermostats and lighting systems) to the places we shop (think pharmacy mobile photo printing, mobile coupons based upon buying preferences) the IoT is already heavily integrated into our lives. Think about all of these connections in our lives today—and now multiply those connections by four. Gartner reports that by 2020, the amount of connected things is expected to rise to 25 billion. What I&O leaders need to know is what is enabling all of these connections and how organizations and businesses are expected to keep up with the growth and manage these links.
As we start looking toward 2016, we see a lot of new and exciting changes on the horizon for workload automation. While automation has always been considered a core foundational piece for IT to manage the IT environments, we’re starting to see a shift as automation is becoming a core driver of innovation and agility for the business. So let’s take a look at what’s to come for workload automation in 2016:
Just a few weeks ago, I had the opportunity to attend Gartner’s Symposium/ITXPO in Orlando, Florida. ITXPO is always a great event filled with a lot of new ideas as well as a forum to speak with IT leaders about their views and experiences on current challenges and new technologies. This year, in particular, I noticed a significant overlap between what Gartner analysts were speaking about in sessions and the challenges and upcoming projects CIOs and IT Managers were talking about on the exhibit floor.
While APIs have been around for more than a decade, today’s API-connected services are emerging as the preferred method for cloud, mobile devices, and virtually any end-point you can name. Most IT organizations are acting as both providers of APIs - creating APIs to provide internal system access, as well as API consumers - connecting their applications to externally provided APIs.