Cloud Path: Smart and Complete Cloud Migration Assessment, Preparation, and Execution

Transcription

1 Cloud Path: Smart and Complete Cloud Migration Assessment, Preparation, and Execution Heejoon Park, Cloud Lead, TIBCO PSG Americas INTRODUCTION According to Forbes, Cloud computing is projected to increase to $162 billion by 2020, attaining a compound annual growth rate of 19%. 1 In addition, 74% of tech chief financial officers say cloud computing will have the most measurable impact on their business in Gartner predicts the worldwide public cloud services market will grow 18% in 2017 to $246.8 billion, up from $209.2 billion in In this context, cloud could mean multiple deployment models involving private, public, or hybrid deployments. This infrastructure will support strategic investments that help your organization achieve agility and faster time-to-market for pushing out new products and features that meet and exceed your customers expectations. These workloads could also include streamlining and automating everyday IT operations and maintenance that free up IT professionals to work on higher-value activities. In addition, most organizations are also adopting cloudbased SaaS applications for day-to-day operations. While the focus of this whitepaper is on migration of existing TIBCO workloads, both current and new customers alike can take advantage of TIBCO s cloud technologies and application patterns.

2 WHITEPAPER 2 MIGRATION OPTIONS For nearly two decades, TIBCO customers have leveraged our software to run their mission-critical and enterprise-scale applications. Most of these workloads were deployed on-premises with a focus on high-availability, fault tolerance, and load leveling/balancing. Capacity planning was an important activity for procuring IT investments; making optimal use of resources paved the way for technologies such as hardware virtualization. The Cloud now enables these same TIBCO customers to leverage the capabilities of various cloud providers (Microsoft Azure, Amazon AWS, Google Cloud), and technologies such as Docker and Kubernetes. With TIBCO s marketleading products and programs, you can continue to run your mission-critical applications across private, public, and hybrid deployments and choose from among multiple migration options and strategies for optimally managing and migrating these investments to your cloud of choice. Industry analysts largely refer to these options as the five Rs, represented as a continuum as shown in the figure below (See Rehost Refactor Rearchitect Rebuild Replace THE FIVE STRATEGIES OF CLOUD PATH The following matrix compares the processes and capabilities of the five Rs in terms of workload destination, degree of modification required, and pros and cons. The Cloud Path Rehost option, commonly referred to as lift and shift, is a relatively quick way to industrialize your applications. With rehost, you can exploit cloud capabilities such as shared and virtual infrastructure on which existing applications would run with minimal change. The Cloud Path Refactor option extends Rehost by leveraging applicable native cloud services such as elastic load balancers or relational database services from a cloud provider. Both Rehost and Refactor options involve mostly configuration changes with the application codebase itself running as-is. The Cloud Path Revise or Rearchitect option reorganizes/restructures your applications or services so that they exhibit characteristics such as automatic dynamic provisioning, elastic scalability, and self-service/on-demand computing. As part of this option, you would adopt a microservices architecture and leverage a platform-as-a-service (PaaS). The Cloud Path Rebuild option is chosen when it s determined that the effort and challenge required to rearchitect your applications exceeds the alternative of rebuilding or rewriting the application. This strategy could be used as part of a larger engagement in which you seek to replace a third-party component.

3 WHITEPAPER 3 The Cloud Path Replace option has you literally replacing the current on-premises products and solutions with a software-as-a-service (SaaS) offering. When considering your cloud migration options, there s no one-size-fits-all approach that can be applied across your entire application portfolio. You ll need to consider factors such as your organization s timeline of cloud adoption, key business drivers for moving to cloud, complexity of current applications, rate of change needed, degree of migration effort, and other considerations. Rehost Refactor Revise (Rearchitect) Rebuild Replace Description Lift and Shift Redeploy to different hardware environment Run apps on a cloud provider s infrastructure Shift to a cloud optimized infrastructure with modified codebase. Rebuild solution, discard existing code, re-architect application Use commercial software delivered as a service Destination Iaas IaaS or PaaS IaaS or PaaS PaaS or SaaS Low Code Modification Infrastructure Configuration Configuration changes, fit target environment Support legacy modernization, then rehost/refactor Lose existing code & frameworks, access platform features Replace existing capabilities with SaaS offerings Advantages Short timeline. lies to in-house and COTS Reuse languages, frameworks, containers in the PaaS Leverage cloud characteristics of provider s infrastructure Improved developer productivity, better tools, community Little development cost, no need to build features Disadvantages Moving without improving, licensing changes Missing capabilities, transitive risk, framework lock-in Potentially a major development project, framework lock-in Framework lock-in Inconsistent data semantics, data access issues, vendor lock-in CLOUD PATH BENEFITS, FEATURES, AND PHASES Cloud Path is a service that applies cloud migration strategies to TIBCO onpremises deployments. It is a TIBCO company-wide, cloud-first initiative that embodies our software vision of being anywhere and everywhere. It: Allows you to move freely between workload types and formulations of workload types (for example, hybrid). Allows you to bridge and leverage existing investments on-premises along with new workload styles in the cloud (microservices, function-as-aservice, serverless). Specifically for SaaS, it provides a single, unified experience across all capabilities and services that can be mixed and matched. Gives you choice and guidance. TIBCO Cloud Path is a comprehensive methodology and related set of solutions, best practices, tools, and accelerators that help you successfully leverage cloud technology. From a TIBCO products and technology perspective, we have painstakingly reviewed each and every product, detailing step-by-step instructions on how to take on-premises deployment to any of the supported migration options. We have put together the overall processes in managing complex migration programs and projects involving distinct phases: assessment, preparation, and execution for all TIBCO products.

4 WHITEPAPER 4 The important piece is how you tie all of the moving parts into a coherent, to-be cloud architecture with reusable assets such as ready-to-use architecture patterns supporting multiple migration options. We have also developed accelerator tools, such as the DevOps and Migration toolkit, to accelerate your migration journey, along with multiple project delivery options including migration factory and a managed services offering. Operational Excellence Improve quality, availability, and security Secure faster time to value Accelerated Innovation Enhance enterprise agility Scale quickly based on dynamic market and business demands Equip for future technology and demands Digital Evolution & Collaboration Optimize your costs and operations Scale and enhance the value of existing on-prem applications The diagram below depicts three phases that are typically followed through in a given Cloud Path journey. Assessment Preparation Execution Cloud Capabilities / Strategy Existing Architecture lications Landscape CloudPath Checklist lications Portfolio Target Cloud Architecture CloudPath Plan Solution Architecture Build Cloud Platform Define Target Architecture Generate Plan and Solution Architecture CloudPath Steps TIBCO Services Difference P CloudPath Planning Tool P Ready-to-use Migration / P Managed Services Design Patterns -TIBCO Product Selection P DevOps Toolkit -Migrating TIBCO BusinessWorks -Platform Configuration 5 / 6, Rehost P CLE Cloud Edition -Product Dependencies -Migrating ActiveMatrix BPM Rehost P TIBCO Hawk Accelerator -Infrastructure Sizing Cloud Edition -Migrating TIBCO MDM Rehost -Infrastructure Costing P Infra as Code Template -... and others - e.g. Terraform / AWS -Planning Checklist CloudFormation P Migration Toolkit - e.g. Cloud Configurator

5 WHITEPAPER 5 In the assessment phase, a cloud architect (CA) from TIBCO PSG works with you to review your current as-is architecture and TIBCO applications landscape. Partnering with you, the CA will also take into account your current cloud capabilities and strategies, key business drivers, and your team s skill set to formulate and validate your target cloud architecture around TIBCO solutions. Having assisted multiple customers in their journey to cloud, TIBCO PSG has developed a standardized Cloud Path Assessment Framework each CA uses for consistent application of TIBCO migration best practices. During the preparation phase, the CA maps the existing TIBCO applications and services portfolio onto the target architecture formulated from the assessment phase. The optimal migration strategy/option from the five Rs methodology will be chosen for each TIBCO application. The CA will leverage ready-to-use migration design patterns from TIBCO s reusable Cloud Path building blocks to accelerate this design phase. Through these activities and steps, the CA will then construct a detailed cloud solution architecture along with a roadmap managing a sequence of project executions based on project priorities, timelines, dependencies, and other criteria. The execution phase is where the solution architecture implementation is actually realized. One single cloud migration project is referred to as a Cloud Path Step as shown in the diagram above. During the execution phase, there could be multiple projects happening at the same time. Typically, the execution phase could start with the initial project that lays foundational cloud capabilities such as DevOps and CI/CD pipeline as shown in the diagram below. The CA leverages relevant artifacts such as infrastructure-as-code scripts from the Cloud Path DevOps Toolkit to accelerate project delivery. Specify Version Control Build Test/Verify Package Repository Deploy Monitoring & Management Maven Sonatype Ansible JUnit Terraform TIBCO Hawk Java Subversion Gradle TIBCO Common Logging & Exception Handler TIBCO CLOUD PATH EXAMPLE: REFACTOR Now that we ve walked you through the overall Cloud Path phases, let s put all these concepts together and show you how you would actually migrate a TIBCO BusinessWorks 5 on-premises application to the cloud. For this example, let s assume that your target cloud architecture for TIBCO solutions has been validated and determined from the Cloud Path assessment phase. During the preparation phase, the optimal migration strategy for different categories of TIBCO BusinessWorks 5 applications and services would be determined. This example explains a TIBCO BusinessWorks 5 Cloud Path Refactor option and shows you the accompanying ready-to-use migration design pattern developed by TIBCO PSG.

6 WHITEPAPER 6 Before we get into the specifics of Refactor, note the available cloud migration options for TIBCO BusinessWorks 5 applications, depicted in the diagram below: Rehost and Refactor options leverage infrastructure-as-a-service (IaaS) as the base cloud-computing model. Refactor extends Rehost by incorporating relevant native cloud services as needed. You can also migrate a TIBCO BusinessWorks 5 application to TIBCO BusinessWorks Container Edition via the Rearchitect option and deploy and run it as a cloud-native application or a microservice on container-based PaaS platforms such as Cloud Foundry, Kubernetes, OpenShift, or similar Dockersupported cloud platforms. Through the Replace option, you can migrate an existing TIBCO BusinessWorks 5 application to run as an integration app on TIBCO Cloud Integration hosted by TIBCO, leveraging an integration-platform-as-a-service (ipaas) computing model. TIBCO BusinessWorks 5 Services TIBCO BusinessWorks 5 Services TIBCO BusinessWorks 5 Services + Native Cloud Services TIBCO BusinessWorks Container Edition TIBCO Cloud Integration On-Prem IaaS IaaS PaaS ipaas Rehost Refactor Rearchitect Rebuild/Replace As-is Architecture To-be Architecture Now the Refactor option. Our example entails a typical group of TIBCO BusinessWorks 5 engines deployed on-premises in a load balanced configuration as shown below. The engines distribute incoming HTTP requests using some policy such as round-robin. The engines are deployed into an administrative boundary called a domain, which requires a persistence layer maintaining application and machine configurations, and other housekeeping data. A typical production setup would require a domain configured against a database instance. Hardware Load Balancer On-premises Host(s) On-premises Host(s) BusinessWorks Process Engine(s) Hawk Rendezvous Adapter SDK Adapters / Plugins Hawk Rendezvous Rendezvous (Enterprise Message Service Server Optional) / Domain Communications Domain Persistence Layer (RDMS)

7 WHITEPAPER 7 For our example, we ll use Amazon AWS as the cloud provider. For using the Refactor option for an on-premises TIBCO BusinessWorks application, you need to install TIBCO BusinessWorks 5.x components on AWS, using the following cloud services: AMAZON VIRTUAL PRIVATE CLOUD (VPC) Insulates / protects the TIBCO BusinessWorks 5.x system. AMAZON ELASTIC COMPUTE CLOUD (EC2) Provides the HA/FT BusinessWorks 5.x systems, Enterprise Message Service systems, and directory services. AMAZON RELATIONAL DATABASE SERVICE (RDS) Provides DB storage for BusinessWorks 5.x (checkpoints, admin repository). AMAZON ELASTIC FILE SYSTEM (EFS) Provides shared file system accessed by BusinessWorks 5.x instances. AWS CLOUD FORMATION Provided CloudPath Step example is based on the Linux bastion hosts on AWS Quick Start deployment (deployed into a new VPC). Spans two availability zones. ELASTIC LOAD BALANCING Distribute incoming application traffic across EC2 instances. AMAZON ROUTE 53 Domain Name System (DNS). As the first step, we recommend that you use the AWS Quick Start using the following link to create the base networking environment on AWS: ( aws.amazon.com/quickstart/latest/linux-bastion/architecture.html#bastion-hosts). As shown below, this setup provides a highly available architecture spanning two availability zones with the following features: A new Amazon VPC configured with a public and private subnet in each availability zone. The private subnets are used to host all the services used by this environment apart from the load balancing instances. A Linux bastion host in each public subnet with an elastic IP address to allow inbound secure shell (SSH) access to EC2 instances in public and private subnets.

8 WHITEPAPER 8 AWS VPC Elastic IPs (public route) Internet Gateway Elastic IPs (public route) Linux bastion instances Linux bastion instances Auto scaling group Public subnet /20 Public subnet /20 Amazon CloudWatch Your workload (not included) Your workload (not included) Private subnet /19 Private subnet /19 Virtual Private Cloud /16 Availability Zone 1 Availability Zone 2 AWS Region On each of the private subnets in an availability zone, install four Amazon Machine Images (AMIs) as follows: Standard base image for TIBCO Enterprise Message Service to support TIBCO Enterprise Message Service based domain communications.* TIBCO BusinessWorks compute instances with TIBCO Rendezvous, TIBCO Runtime Agent, and TIBCO BusinessWorks 5 runtime. TIBCO BusinessWorks Adapter instances with Rendezvous, Runtime Agent, and Adapter runtime (as needed). TIBCO Admin Image with Rendezvous, Runtime Agent, and TIBCO Administrator runtime. Amazon EFS for domain file storage requirements such as logs. Amazon RDS for DB-backed domains and checkpoint data. JDBC-compliant database * For detailed step-by-step instructions on how to configure a TIBCO Enterprise Message Service fault tolerant environment on AWS, refer to: tibco.com/wiki/tibco-enterprise-message-service-fault-tolerant-configurationamazon-aws

9 WHITEPAPER 9 The following figure shows the mapping of the TIBCO BusinessWorks 5.x runtime environment onto the private subnets across availability zones. AWS VPC Internet Gateway Public Public Linux bastion instances Linux bastion instances Private Private BW 5.x Runtime Environment (BW Runtime, Hawk, RV (TRA)) Virtual Private Cloud Availability Zone 1 Availability Zone 2 AWS Region The intent of this paper is to provide a quick introduction to TIBCO Cloud Path and not to be exhaustive in coverage and capability. For exact steps and complete details including products not covered here, we encourage you to reach out to our TIBCO PSG team at services/consulting. Note the following deployment considerations: You can utilize Enterprise Message Service for domain communications. Scaling of individual TIBCO BusinessWorks processes will depend on the type of process starter used: HTTP: the hardware load balancer would be replaced by a cloud elastic load balancer service such as AWS ELB. JMS: no additional cloud service is required because multiple JMS clients can consume from the same queue for load balancing. Configuration of Rendezvous in using localhost option only. TIBCO CLOUD PATH EXAMPLE: REARCHITECTURE In this example, we ll explore the Rearchitect migration option for TIBCO BusinessWorks 5.x. This option leverages platform-as-a-service (PaaS) as the base cloud computing model. Your existing TIBCO BusinessWorks 5.x application needs to be migrated into a TIBCO BusinessWorks Container Edition app. The following figure depicts the TIBCO BusinessWorks Container Edition architecture between design and runtime environments. To migrate, you can use the out-ofthe-box migration utility in the TIBCO Business Studio integrated development environment (IDE), based on Eclipse. Developers would also use TIBCO Business Studio to build new cloud-native applications. Once the application has been migrated, you ll need to build a deployment artifact as an enterprise archive (EAR) file via the build process that can be done in the IDE directly or automated as part of the continuous integration (CI) pipeline.

10 WHITEPAPER 10 PaaS BWCE Container TIBCO Business Studio Design-time in Eclipse BWCE Buildpack or Docker Image Deploy lication Module Design-time lication Shared Module 1 Shared Module N Build EAR File Deployment Artifact Depending on the PaaS of your choice, you ll either need to use TIBCO BusinessWorks Container Edition Buildpack or TIBCO BusinessWorks Container Edition base Docker image to construct an immutable, self-contained app image that contains your deployment artifact along with any client libraries you need, such as in Enterprise Message Service, and database jars. This final app image is then deployed onto the PaaS of your choice. This is illustrated on the right side of the diagram above. This newly created or migrated cloud native TIBCO BusinessWorks Container Edition application/microservice can run in containers on-premises, in the cloud, and in popular PaaS environments such as Cloud Foundry/Openshift/Kubernetes, all without change or re-coding. TIBCO BusinessWorks Container Edition and plug-ins are also available on AWS Marketplace leveraging native features of AWS Elastic Container Service (ECS) or your choice of Docker-based PaaS for container management, giving you flexibility to scale on demand and manage software cost as you go. Note that TIBCO BusinessWorks Container Edition was built specifically for cloud-native microservices and containerized deployments and offers the following tooling support: Configuration management Service registry and discovery tooling Support for circuit breaker patterns The following figure represents the Interconnect Everything reference architecture showing multiple layers of cloud computing models to which TIBCO BusinessWorks 5.x application could be migrated. For TIBCO BusinessWorks 5.x applications that run either on-premises or as refactored leveraging IaaS, the software itself contains run-time support for monitoring, management, and other administrative capabilities (such as domain). It is an example of an integration platform. On the other hand, TIBCO BusinessWorks Container Edition runtime is specifically optimized for containerized deployments and runs natively on Cloud Foundry, Docker, and other container/cloud platforms leveraging the underlying platform s capabilities for management, logging, and monitoring. In this context, TIBCO BusinessWorks Container Edition functions as an integration framework.

11 WHITEPAPER 11 As you move more of your application workloads of different types to common runtime environments such as PaaS specific technology differences for each application type is abstracted within a container boundary. This allows the PaaS to treat these applications in a consistent manner throughout its lifecycle, allowing overall simplification in management of your IT environment. With that in mind, you have the option of utilizing the TIBCO provided container monitoring app and/or the tools that come with the container-as-a-service (CaaS) or PaaS; we support and work with each of the tools. Management Platform Integration Platform PaaS Integration Framework ipaas Orchestration lications Services Adapters & Plugins Monitoring & Management Container Container Container BWCE JAVA NODE Integration Scalability Dynamic Provisioning Service Broker Health Monitoring Choreography Creation & Mocking Logging, Integration Monitoring, Framework and Management On-Prem IaaS Microsoft Azure openstack The other important driver to consider for the Rearchitect option using TIBCO BusinessWorks Container Edition is the time-to-market factor. The key question is no longer how many innovations your organization can produce, but at what pace you can bring new ideas to market. Are your organization and development environments agile enough to seize opportunities while they matter? As a higher productivity enabler, many organizations are adopting PaaS to simplify and automate how they develop, deploy, and manage software lifecycles from dynamic provisioning of infrastructure in a self-service/on-demand manner to sophisticated elastic scaling of compute resources as loads change. As developers are relieved from low-level setup and run tasks, they can focus on higher-value activities and iterate faster. TIBCO BusinessWorks Container Edition is a first-class citizen in every major cloud/ container platform. It brings the four pillars of agility for developing microservices, cloud-native integration apps, and choreography as shown below. Container BW Technology (PaaS/CaaS) PaaS Container Container JAVA NODE Integration SaaS Architecture (MSA, 12 factor app LIFESPAR, Cloud Native) Tools & Process Automation (CI/CD) Culture and Org (DevOps) IaaS Microsoft Azure openstack On-Prem Legacy

12 WHITEPAPER 12 The next two diagrams show you how TIBCO BusinessWorks Container Edition and other TIBCO and third-party technology components, can be deployed in Cloud Foundry and OpenShift. iphone.com Web Android Android ROUTER HEALTH MGR LOGGING CONTROLLER NATS SVC BROKER BusinessWorks BusinessWorks BusinessWorks BusinessWorks ORACLE Services provisioned manually through cups MongoDB BusinessWorks Node Web app JAVA PostgreSQL Cloud Foundry Containers redis TIBCO ESB TIBCO eftl Enterprise BusinessWorks 6 Message Service Provisioned through a service broker The diagram above shows how TIBCO BusinessWorks Container Edition applications can be deployed in the same ecosystem as other technologies to build your app. For example, you may create a web application in Spring and deploy alongside REST services in TIBCO BusinessWorks Container Edition that use TIBCO FTL messaging exposed as a service and a PostgreSQL database deployed in Cloud Foundry. Routing Layer Developer Master / Authentication Pod Node Pod Pod Node Pod Node Pod Pod node.js Persistent Storage MySQL SCM (Git/Svn) Data Store Scheduler RHEL RHEL RHEL Node Node Node Pod Pod Pod Pod Pod Pod CI/CD Management / Replication MongoDB MongoDB MongoDB Existing Red Hat Enterprise Linux RHEL RHEL RHEL Automation Toolsets Service Layer Operations Physical Virtual Private Public

13 WHITEPAPER 13 OpenShift supports Docker as the software container format for packaging standardized units of applications that are then managed by Kubernetes for scheduling, replication, and orchestration. OpenShift also introduces capabilities like routing for easily exposing services running on its clusters without requiring separate cloud services such as AWS Route 53. It also offers -based streamlined integration of CI/CD capabilities. The diagram above shows how migrated TIBCO BusinessWorks Container Edition applications would be running in the OpenShift environment. SUMMARY Whether you are looking to industrialize your existing applications or innovate faster by moving from monolithic applications to ecosystems of cloud-native microservices, cloud-computing technology supplies essential building blocks that can drive and sustain your digital transformation. And whether your core TIBCO footprint includes TIBCO BusinessWorks 5, Enterprise Message Service, TIBCO ActiveSpaces, and/or TIBCO ActiveMatrix BPM from our Interconnect Everything category or encompasses deployments including TIBCO BusinessEvents, TIBCO Spotfire, or TIBCO MDM from our Augment Intelligence group, TIBCO Cloud Path can help you find the optimal migration strategies to chart your journey to the cloud and realize all its benefits. For more in-depth information on TIBCO Cloud Path, please contact the TIBCO PSG team ( /# e Global Headquarters 3307 Hillview Avenue Palo Alto, CA TEL FAX TIBCO fuels digital business by enabling better decisions and faster, smarter actions through the TIBCO Connected Intelligence Cloud. From s and systems to devices and people, we interconnect everything, capture data in real time wherever it is, and augment the intelligence of your business through analytical insights. Thousands of customers around the globe rely on us to build compelling experiences, energize operations, and propel innovation. Learn how TIBCO makes digital smarter at , TIBCO Software Inc. All rights reserved. TIBCO, the TIBCO logo, ActiveMatrix, ActiveSpaces, Enterprise Message Service, Hawk, LogLogic, Rendezvous, Spotfire, TIBCO Business Studio, TIBCO BusinessEvents, TIBCO BusinessWorks, TIBCO Cloud, TIBCO eftl, TIBCO FTL, and TIBCO Runtime Agent are trademarks or registered trademarks of TIBCO Software Inc. or its subsidiaries in the United States and/or other countries. All other product and company names and marks in this document are the property of their respective owners and mentioned for identification purposes only. 01/31/18