Navigating Cloud Adoption: Trends that Challenge and Inspire Designers
•
2 likes•154 views
Maureen Flemming of IDC gave the keynote at Red Hat's "Microservices, Containers, APIs and Integration Day" in New York and DC, August 2018
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Navigating Cloud Adoption: Trends that Challenge and Inspire Designers
Similar to Navigating Cloud Adoption: Trends that Challenge and Inspire Designers (20)
More from Judy Breedlove
More from Judy Breedlove (12)
Recently uploaded
Recently uploaded (20)
Navigating Cloud Adoption: Trends that Challenge and Inspire Designers
- 1. Naviga&ng Cloud Adop&on: Trends That Challenge and Inspire Developers Maureen Fleming Vice President
- 3. [CATEGORY NAME], [PERCENTA GE] [CATEGORY NAME], [PERCENTA GE] 2016 Source: IDC Worldwide 2016 & 2018 CloudView Surveys 2016 N=11,350; 2018 N=9,520 3 Public Cloud Is Mainstream [CATEGORY NAME], [PERCENTA GE] [CATEGORY NAME], [PERCENTA GE] 2018 44% 4% 4% 48% No Plans Considering This year Using 46% 5% 5% 45% No Plans Considering This year Using While public cloud spending grew rapidly over the past decade, cloud adop6on has only gradually increased As public cloud becomes mainstream, more enterprise mission cri6cal workloads are moving into cloud
- 4. Public and Private Cloud Source: IDC Worldwide 2018 CloudView Surveys 2018 N=5,740 • Of enterprises that adopted cloud: • Increasingly organizing new development projects to deploy as cloud architecture (53% cloud also and cloud first) • Best fit (28%) reflects reality that not all new projects are cloud suitable 4 Cloud Adop&on Posture for Net New IT Services 26 27 15 28 3 Cloud First Cloud Also Cloud Last Best Fit No consistent approach
- 5. 5 Containers Represent a Different Kind of Deployment Scale
- 7. Virtual cloud compute Virtual servers on- demand. Pay by use, and premium reserved access Elas6c scaling guarantees access to correct level of compute Examples: • AWS EC2 • Azure Compute • OpenStack Compute • Etc. 7 Cloud Compute Op&ons Container-based compute Opera6ng system virtualiza6on that runs an applica6on and its dependencies in resource- isolated processes (Docker). Includes an orchestra6on system (Kubernetes) to: • Automate deployment • Scale • Manage containerized applica6ons Examples: • Red Hat OpenShik Container Plalorm • AWS Fargate (CaaS), ECS • IBM Cloud Private Serverless compute Stateless processing of code in response to an event, which triggers the upload of stored code, executes the code for a set period of 6me and then terminates Serverless provides service on- event by managing the underlying compute resources. Developers have no addi6onal deployment considera6ons beyond cost per use Examples: • AWS Lambda • Microsok Azure Func6ons • Google Cloud Func6ons Bare Metal A computer system or network with the virtual machine installed directly on hardware rather than within the host opera6ng system Examples: • AWS Bare Metal Instances • IBM Cloud Bare Metal Servers • Tradi6onal servers running hypervisors
- 8. Virtual cloud compute 8 Cloud Compute Op&ons Container-based compute Serverless compute Bare Metal Most common compute for na6ve public cloud custom solu6ons Viral adop6on, especially to develop on private cloud and deploy in private or public Viral adop6on for experimental, intermi;ent, single func6on or pipeline- oriented workloads High performance workloads, legacy workloads Within the next 3 years • Vendors will make their middleware available to run in containers, in a serverless configura6on and on bare metal • Vendors will support different pricing models, including elas6c, consump6on-based pricing • Development teams will be able to shik between deployment op6ons using the same middleware. Choices will be based on an op6miza6on of cost efficiency and performance requirements
- 9. 9 © IDC SAP IBM Google Oracle Microsok Salesforce AWS Enterprise DataCenter Hos6ng Managed Container Pla/orm For the past decade, enterprises have been following vendor’s to the cloud. Cloud plalorm providers have focused on building capabili6es to the North and South Disrup6on is coming East to West via container plalorms Container plalorms are becoming the atomic unit of PaaS for enterprise custom solu6ons and for assets that need to run across loca6ons and ecosystems
- 10. 10 Top Drivers for Container Adop&on IDC, January 2018. N=301
- 12. More spending on development of custom solu6ons (77%) than adop6on of new SaaS (23%) Solu6ons based on custom code and commercial PaaS services combine custom code and commercial cloud sokware • 17% of new spending on PaaS will involve custom development • 13% will involve implemen6ng PaaS commercial services Development in private PaaS may be deployed in same environment or hosted on a public cloud. • Control over development and loca6on flexibility are important drivers of container adop6on % of New Cloud Applica&on Spending Source: IDC Worldwide 2018 CloudView Survey 2017 N=5,168 12 [CATEGORY NAME], [PERCENTA GE] [CATEGORY NAME], [PERCENTA GE] [CATEGORY NAME], [PERCENTA GE] [CATEGORY NAME], [PERCENTA GE]
- 13. Microservices An approach to developing a single applica&on or backend service as a suite of small services, each running in its own process • Services are independently deployable • Bare minimum of centralized management of these services • WriMen in any programming language • Uses lightweight protocols for communica&ons: HTTP API, messaging • Maintains clean separa&on of stateless and stateful services Note: The applica&ons or backend services constructed from microservices are accessed via secure API Gateway, which is oQen implemented as a component of API Management SoQware. • Individual microservices have APIs but connect with each other through inter-communica&ons mechanisms 13 39% 42% 34% 38% Implemented Planning to 2018 2017 Source: IDC CloudView Survey, N=1,446 Microservices adop6on by developers in organiza6ons that have adopted cloud Defini6on from mul6ple sources, but primarily Mar6n Fowler The term Microservices has become more fashionable in the non-technical community; the meaning is changing to now be thought of as a limited scope service externally callable using a public or permissioned API
- 14. Func&ons Func&ons soQware provides stateless processing of code in response to an event • Spending on func&ons was viral in 2017, with growth exceeding 200% Most middleware vendors have introduced a func&ons capability either as a public cloud offering or in a container • Apache OpenWhisk is the most common open source distribu&on of Func&ons • AWS Lambda is the first commercial implementa&on, largest and best known Func&ons is oQen equated to serverless, and at its most basic configura&on, becomes the callable layer of serverless compute. • Serverless is a larger category associated with a style of deployment. Func&ons is a segment of serverless There are varia&ons of func&onality across the different Func&ons products. Some are basic, while others have added condi&onal logic and stateful processing 14
- 15. Pipelines Data pipelines are popularized as a workflow to deliver data from source to target that may involve different types of transforma&ons and data enrichment. Pipelines are being re-constructed to support the event- condi&on-ac&on design paMern of an event-driven architecture to detect and predict problems as a way to focus on preven&ng problems or iden&fying opportuni&es AI used to convert unstructured content to a data model; machine learning algorithms detect anomalies and make predic&ons and recommenda&ons. This combines with different types of middleware: • Messaging middleware • Integra&on soQware • Business rules • Func&ons 2017 spending for ECA pipelines grew in mid-double-digits 15 Event Process Analyze Act Decide Event processors receive and process data streams Streaming analy6cs detect and predict when decisions need to be made Decision automa6on determines whether and what ac6on is required and routes instruc6ons Applica6ons receive and execute instruc6ons Condi6on Evalua6on Use cases • Lost baggage detec6on • Customer sen6ment • Imperfect order
- 16. Robo&c Process Automa&on Robo6c sokware automa6on (RPA) is sokware designed to automate or augment repe66ve manual tasks • RPA uses client agent to intercept instruc6ons between an applica6on and the OS and re-routes to the RPA plalorm to execute the bot or calls the bot and executes on the client • Determines how to automate by recording work end users do and building playbook mechanisms from the recording • Other types link together automa6on object models and then run them as they are triggered RPA is viewed by businesses as a strategic automa6on technology and funding RPA COEs Architecture teams view RPA as one type of automa6on that can be applied to automa6on use cases RPA grew in triple digits in 2017 and the leading vendors have $1B plus valua6ons 16 AI Pla/orms Robo6c Process Automa6on Workflow & Integra6on Middleware Automa6on- Embedded Applica6ons
- 18. We are in an era of decentralized compu6ng • Public cloud adop6on is an accelerator of decentralized compu6ng • Most organiza6ons that adopt public cloud adopt mul6ple clouds • All of these clouds tends to connect to on- premises or third party hosted applica6ons built on tradi6onal infrastructure Three ways to make decentralized compu6ng easier to manage • Hybrid approach to integra6on • Shik to containers-based bespoke that offers the op6on to co-locate where needed • Asynchronous messaging Bespoke Clouds: $28B Applica6ons Clouds: $90B 18 Amazon 49% IBM 7% Google 7% Salesforce 6% Microsok 23% Others 8% [CATEGORY NAME], [PERCENTAG E] [CATEGORY NAME], [PERCENTAG E] [CATEGORY NAME], [PERCENTAG E] [CATEGORY NAME], [PERCENTAG E] [CATEGORY NAME], [PERCENTAG E] Rest of Market 73%
- 19. API Management Integra6on Messaging Secure Gateway Integra6on Development Studio Developer Portal Mapping Tools Visual Development Monitoring No6fica6ons Analy6cs Logging Integra6on and connec6vity are key assets of decentralized compu6ng • API management with a secure API gateway • Shared catalog of services • Support for embedded microservices pipelines • Common, shared integra6on services • Asynchronous, reliable messaging Mul6-cloud deployment capabili6es that also support container deployments 19
- 20. But integra6on and connec6vity are not enough unless they are hybrid Integra6on solu6ons are called hybrid when their sokware components can • Be deployed in different loca6ons • Communicate across loca6ons and share common assets • Integra6on and interoperate with other integra6on tools 20 Deployment and Execu6on Hybrid Integration Services Shared Integration Libraries and Services Catalogs AdministratorsData Scientists Semi-Pro Developers End UsersDevelopers Internal B2E Applications and Services External Ecosystem Partners (B2B) Consumers (B2C) Batch Request-ResponseEvent-Driven Data Services Business Logic Services MobileOn-Premises Cloud Edge Stateless Stateful Governance Development ManagementDiscovery Measurement Mobile IoT AR/VR BOT Connected Processes Assets People API Databases Stream Processing AI/MLAnalyticsData Lake Decision Support & Automation Workflow Developer Roles:
- 21. 21 Recipes Workflows Tasks En66es Templates Forms Conversa6ons/ Bots Connec6ons Orchestra6on Data Mapping Template Builders Onboarding Messaging Pa;erns Applica6on Microservices Integra6on Services Transforma6ons Pipelines DevOps Do-It-Yourself Tier • End users • Non-Developers • Developers • Partners Non-Developer IT • DBAs • Integra6on admin. • Business analysts Developer • Integra6on specialists • Developers • Sokware engineers API Catalog Developers build and product manage digital u6lity services Semi-pro developers use low code tools to package u6li6es into composite services; connect to 3rd party APIs End users work with simplest no code tools to handle personal & team automa6on Integra6on COE • Enables self-service access to APIs • Provides governance framework around shared services • Manages services catalog, plug-in libraries • Maintains usage metrics • Iden6fies and tracks high value APIs • Builds integra6on services • Supports integra6on innova6on with R&D
- 23. Recommenda&ons Make an effort to experiment with events, func6ons and microservices Start planning a POC for a re-plalorming project using a container plalorm • Provides “before” and “aker” cost comparisons • Look for projects that have varia6ons in u6liza6on • Your savings should become the basis for your business case to move forward Begin to assess your integra6on capabili6es • How decentralized is your compu6ng? • How well suited are your exis6ng capabili6es to operate in a decentralized architecture? • Does you integra6on and messaging support the breadth of pa;erns you need, including embedded pipeline and messaging pa;erns? • Does your current integra6on slow down applica6on implementa6on projects and bespoke development? Services and their APIs should be managed as products • COE should want to manage high value APIs, but those types of APIs need to be managed and marketed • Documenta6on is cri6cal, including descrip6ons of func6ons, use cases and quick starts • Marke6ng includes making the APIs shareable and auto-discoverable 23