Download - Adopting Cloud & Roadmap

Kevin Bohan

Director of Product Marketing

Integration Technologies, TIBCO Software

Adopting Cloud – Why, When, and How?

Webinar Recording

Today’s webinar is being recorded and a link to the recording will be emailed to all webinar registrants

Have A Question?

Submit questions using the Q&A panel

Housekeeping


Ben Franklin Did Not Take Cloud Computing Into Account

It’s Not a Question of If, It’s a Question Of When

Top Reasons for Use of Public Cloud Services

•  IT Modernization • Cost Savings

•  Innovation

• Agility

•  Improved Application Development



Cloud Offers Many Benefits, But You Must Plan for a Hybrid World

This Will Include Leveraging Existing On-Premise Investments

Options for Migrating Applications to the Cloud, If You Migrate

Rehost


Refactor Rearchitect Rebuild Replace

Leverage Existing Investment Reinvest

Replace, Leveraging SaaS Based Services

Rehost Refactor Rearchitect Rebuild


Replace


Replacing, Leveraging Commodity SaaS Offerings


Virtually Every Organization Will Leverage SaaS

Replacing, Leveraging Commodity SaaS Offerings


Benefits: •  Full Application is Made Available •  Pay for What You Use •  Everything You Need Out of The Box


With SaaS, Everything You Need Is Hosted For You


However, Customization Is Often Needed


You Also End Up With Islands of Data


The Other Challenge, Does Commodity SaaS Differentiate?

Rehosting, Leverage Existing Investments

Refactor Rearchitect Rebuild Replace


Rehost



•  Lift-and-Shift Approach to Cloud Hosting

•  Leverages IaaS

• Minimal Changes to Apps, But What Cloud Benefits Are Truly Achieved?

Rehosting


IaaS: The Hardware, Network and Storage is Hosted for You

The Five Characteristics of a Cloud Computing Model

1.  Uses Dynamic, Shared and Virtual Infrastructure 2.  Scales Rapidly and Elastically

3.  Is Available Across Common Networks

4.  Offers a Service in an On-demand, Self-service Model

5.  Meters Consumption


Refactor, To Begin To Take Advantage of Cloud Computing

Rehost Rearchitect Rebuild Replace


Refactor



• When to Refactor: When leveraging existing application is optimal and the application fits well with cloud providers platform

• When Not to Refactor: When an application cannot easily be adapted to meet provider's restrictions or when skills to rebuild existing code are unavailable

When to Refactor


• Code Needs to be Modified

• Could Benefit from Some Elasticity and Better Resource Utilization

• Have Option to Use IaaS or PaaS

Refactor, To Begin To Take Advantage of Cloud Computing


PaaS, Hides Complexity of Infrastructure from Developers


Platform as a Service (PaaS)

A PaaS allows customers to develop, run, and manage applications without the complexity of building and maintaining the underlying technology Capabilities provided include:

•  Robust Scalability •  Health Monitoring •  Dynamic Provisioning •  Public or Private

Refactoring is unlikely to allow you to take full advantage of cloud characteristics


The Challenge

When an application is able to take full advantage of cloud characteristics such as elasticity, on-demand provisioning, network accessibility and resource pooling it is referred to as Cloud-Native.



High availability and web scale requires you to architect your applications differently, they are: • Decoupled from Underlying Infrastructure

• Stateless

• Designed to Deal with Failures

• Dynamically Scaling Up/Down

Key Characteristics of Cloud-Native Applications

Traditional Cloud-Native

Application

Infrastructure

Application

Infrastructure

Consumer

Provider

Platform Interface

Infrastructure Interface

This is what you

have.

This is what you

need.

O/S, Middleware, Runtime

Virtualization, Storage,

Networking

Platform as a Service

Infrastructure as a Service

Availability Policies

Availability Policies

A True Cloud-Native Approach Requires Rearchitecting or Rebuilding

Rehost Refactor Replace


Rebuild Rearchitect



The Benefits of a Cloud-Native Architecture


Innovate Faster/React More Quickly to Change


Operate at Web Scale


But It Takes More Than Just a Cloud Infrastructure


A Continuous Delivery Process

Produce software in short cycles, ensuring that the software can be reliably released at any time


Adoption of a DevOps Culture

Requires development and operations to work closely, focusing on automating software delivery and infrastructure changes.


The Automating of Software Delivery in a DevOps Environment

Developer Laptop

Bare-Metal Server

VM on Hypervisor

Public Cloud

Development Test Production

Continuous Integration Containers: Run Apps Anywhere


Just One More Thing About Containers

Containers vs. VMs


Microservices, an Architecture for Building Cloud-Native Apps

Independent processes, focus on small task, facilitating a modular approach to system-building.


Improve Development Agility, Deployment Flexibility, and Scalability

The granularity and independently deployable container approach simplifies scaling, changing, and adding of functions fostering a Continuous Delivery approach.


Gartner has coined the term “miniservice” and has identified the following characteristics that differentiate the two:

Gartner: By 2017, more than 90% of organizations that try microservices will have found the paradigm too disruptive and be using miniservices instead

Microservices vs. “Miniservices"

Source: Innovation Insight for Microservices Published: 27 October 2015 ID: G00275279 Analyst(s): Anne Thomas

For the purposes of our talk, let’s consider them the same thing for now, whole the distinctions are important, not at this level.

"You Say Tomato, I Say Tomato"


Cloud-Native Platform for the Digital Enterprise



Cloud-Native Platform for The Digital Enterprises

•  Microservices •  API-centric •  Continuous Integration •  Continuous Delivery •  Agile Self-Service

Why? •  Powers Digital Transformation •  Leverage Benefits of Cloud •  But Retain Control •  Replace Legacy Monolithic Java EE

MicroservicesContainer


API

BW

Java

On-

Prem

Le

gacy

Inte

grat

ion

Mic

rose

rvic

es

WS

PaaS SaaS

API

IaaS


Nod

e

API

API

API


Cloud Speed and Agility Requires an API-Centric Approach

To remain competitive, companies must move beyond being cloud adopters and become cloud companies themselves

APIs, Speed Development

APIs allow developers to leverage existing services and focus on differentiated aspect of their application Your partners and customers will be looking for services to reuse, you need it to be your services not your competitors


How To Get Started What Are Others Doing for their Migration to the Cloud?



Your Migration Strategy Must Be On An App-by-app Basis


It is unlikely these migration will lead to your digital business transformation

Avoid the Temptation of the Small and Straightforward Migrations

Establish a standard for integrating various SaaS systems with corporate resources


Break Down the Island of Data SaaS Has Created

q  Rehost q  Refactor q  Rearchitect q  Rebuild q  Replace

•  Harness the data and capabilities of your legacy systems, only rearchitect, rebuild or replace when they are at end of life

•  Utilize a tool that can expose existing functionality as modern REST-based APIs


Leverage What The Digital Startups Lack, Your Existing Assets


Hide the complexities of the unique APIs for the various backend services and provide a consistent easy to use interface to work with these systems. (ex. mainframe, SAP, DBs etc. or net new SaaS applications such as Salesforce, Workday, Marketo, etc.)


Simplify The Connecting of Various 3rd Party Apps and Services


You will need to compose multiple microservices or APIs, into a single application or API to make them easier to consume. Provide your developers with a tool that will simplify:

•  Integrating the various services •  Managing these APIs and secure them for access internally or externally


The Choreographing of Your Microservices



API Management Is Critical in Building This New Digital Ecosystem

• APIs are at the core of modern applications •  Mobile apps, multichannel customer engagement, composite

applications, IoT, microservices

•  Transition from applications to application ecosystems

• Enable the flow of data across domains and boundaries (virtual edge for the enterprise) •  Foundation for new business models •  Virtual storefronts, crowd-sourced development, new value

chains


APIs Bring It All together

The business goals are to improve the responsiveness of the organization and drive innovation. So ensure the tools you select support:

•  An API-centric Approach •  Continuous Delivery •  Continuous Integration •  DevOps •  Containers •  Cloud Native Architecture


Keep Business Goals In Mind


Next Steps


TIBCO Software has helping thousands of organizations in their transition to a digital business. Reach out to your local TIBCO

representative who will be happy to assist you. www.tibco.com


Audience Q&A

Submit your questions using the Q&A panel

Share Your Feedback!

Download - Adopting Cloud & Roadmap

Top Related