Cloud Native: How Developers Are Creating the Experiences of the Future with Cloud Computing
In today’s programming landscape, operating in the Cloud is a given. What began as an inexpensive way to structure information (hello, Intranet) has become a centralized location for multi-device experiences. With Adobe I/O, our team is leveraging the availability of Cloud computing in a way that blurs the lines between tool and workflow, resulting in helpful solutions to increase content velocity and forge the next generation of collaborative tools. The term ‘cloud native’ has bubbled up as a catch-all description of programmers operating in this language; so what does it really mean?
We sat down with Ryan Stewart, group product manager for Adobe I/O, to learn more about how Adobe I/O uses the Cloud, and what ‘cloud nativity’ really means.
What does it mean to be cloud native?
By offering Adobe APIs to developers, Adobe opens itself up to a number of new ways of thinking about services and usage. With ‘touch,’ for example, the developer has to think about how their program can scale and translate across multiple touch points. The developer must also consider a number of new factors when designing their program: how do you go from typing a command into your phone to conversing with Alexa in a fluid, intuitive manner?
“Being cloud native means you’re thinking API first,” said Ryan Stewart, product manager for Adobe I/O. “It’s how certain services manifest themselves across new program applications, how those services will be realized in the hands of new developers.”
To Ryan and the Adobe I/O team, thinking about the multiple ways future users could interact with I/O-enabled technology is a part of being cloud native.
“By Adobe I/O standards,” said Stewart, “being cloud native means building out a program’s infrastructure in a way that leverages all the ways that the Cloud can process and present information.”
Ryan’s point brings us back to the notion of being API first, and thinking about the Cloud as a central source of information and a tool that informs interaction expansion. Many of these touchpoints, such as voice-activated home helpers or smart lights, are not going to be able to process information individually. True cloud nativity will mean leveraging the Cloud as a centralized information hub.
The challenges and benefits of cloud nativity
Cloud nativity also speaks to a new and unique direction for future development projects. By centralizing our information and playing off previously-established foundations, we return (again!) to the centrality of a program’s API.
This does present a unique challenge: developers need to think more holistically about the scale of their project. With so many ways a user can interact with an application, developers are going to be asked not just to program more, but to think about the usability of their product from many different angles. Their success is going to rely on providing multiple modes of interaction, and then creating intuitive ways to connect with the program.
Adobe I/O is built to help developers make that mental transition by offering a more seamless technical experience. Through the Cloud, Adobe is better able to expose content and functionality to developers with better access to Adobe services. I/O is successful because of Adobe’s move to the Cloud, and the increased ability to provide developers with access to our solutions and data.
Better workflows, more automation
A single location for knowledge and content has a huge number of benefits. Firstly, it will become much easier to orchestrate workflows around that content. The services in the Cloud that can manipulate or work with content to improve efficiency will help manage content velocity. A huge aspect of content velocity involves machine learning or AI. With time and program development, Adobe I/O will be able to help automate or provide some additional value to content by simply adding it to the Cloud. By having such a huge number of assets stored in the cloud, I/O users get access to the computing power to deploy services like deep learning and AI. The more information we can get into cloud services, the better off every developer’s projects will be.
Enterprise developers can tap into Adobe’s AI technology using using Adobe Sensei functions. They can create automated processes that run assets, like images, through multiple machine learning algorithms. This allows you to perform actions like auto tagging, auto scoring, and auto cropping, eliminating the need to do these tasks manually. The end result is a streamlined asset approval workforce that can be customized for a user’s specific needs, along with the ability to take an asset from creation to ready-to-use in your centralized asset management system much quicker. You also don’t need to worry about server setup; the whole process takes place in Adobe I/O Runtime, Adobe’s serverless platform.
Big ideas for better development
effects and opportunities of a program, developers learn how to conceive new ways of experiencing their programming, and different means of interacting with it. With Adobe I/O, we are creating a next generation platform that is infinitely scalable, built from the ground-up with intelligence services in mind and capturing decades worth of expertise in managing content and data within our applications.