DOCSLIB.ORG

Journey to the Cloud with IBM Cloud Pak for Applications

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Journey to the Cloud with IBM Cloud Pak for Applications Journey to the cloud with IBM Cloud Pak for Applications Constant innovation IBM Cloud Pak™ for Applications is a set of tools and technologies that enables an organization to modernize its application portfolio on top of Red Hat® OpenShift®. IBM Cloud Pak for Applications helps organizations quickly build and deliver new solutions by enabling users to containerize their workloads, develop cloud native applications using microservices and leverage continuous integration / continuous delivery (CI/CD) capabilities. The application modernization journey Many organizations may have a portfolio of existing Java™ applications created over the last 20 years. Depending on the size of an organization’s application portfolio, the application modernization journey can be a multi-year process. Currently, only 20% of workloads are in the cloud1 due to the effort and complexity of the modernization journey. Cloud Pak for Applications can help these organizations maintain those applications in traditional WebSphere®, move applications to WebSphere in a container, move to WebSphere Liberty in a container, refactor existing applications, and build new cloud native applications in a variety of runtime environments, such as NodeJS. Transformation Advisor Included in the Cloud Pak for Applications is the Transformation Advisor that helps organizations along their modernization journey. Transformation Advisor analyzes existing J2EE applications from WebSphere and assesses the effort to migrate an application to WebSphere Liberty. The output report from the Transformation Advisor allows an organization to figure out which applications can move easily, and which ones are better left on WebSphere. Based on the level of difficulty, users can decide when and which WebSphere applications can move to WebSphere in a container. Throughout the modernization journey Cloud Pak for Applications licensing allows organizations to continue to run their traditional WebSphere without incremental charges while transitioning to Liberty containers. For applications that are being moved to containers, organizations may choose to refactor into micro-services. Organizations developing new applications can design their applications to be cloud native using the latest tools and modern runtimes from Cloud Pak for Applications. Figure 1, The Application Modernization Journey, shows the Transformation Advisor’s role in application development and management that Cloud Pak for Applications provides. The journey starts with the Transformation Advisor to help identify which applications are best containerized through 1) replatforming, 2) repackaging, or 3) refactoring. Then Cloud Pak for 1 https://www.ibm.com/blogs/cloud-computing/2019/03/05/20-percent-cloud-transformation/ © 2020 IBM Corporation IBM IT Economics Consulting & Research Application provides tools to build, deploy, and run the applications in a containerized cloud environment as traditional, cloud ready or cloud native applications. Replatforming versus repackaging Replatforming entails taking an application, such as a traditional WebSphere application, and putting it in a container running the same environment. Putting the application in a WebSphere container does require some Python code to set up the WebSphere application configuration during container build time, but it is a simple way to leverage the security, reliability, and scalability benefits of a modern container platform, without needing to create a WebSphere Liberty profile. When an application is replatformed into a WebSphere container, the benefits of cloud operations (ease of provisioning, availability, and scalability) are immediate. Repackaging involves taking an application, such as a traditional WebSphere application, and rebuilding it to run in a WebSphere Liberty container. Repackaging requires even less effort than replatforming an application, and it offers many benefits for small agile development, microservices, and multi-cloud Figure 1 The Application Modernization Journey illustrates three migration approaches, replatform, repackage and refactor to transform applications for a containerized cloud environments. WebSphere Liberty provides a light weight, composable application server designed to run in a container environment. Because Liberty servers only install and run the features requested and/or needed by the application, less compute and storage resources are consumed. WebSphere Liberty is ideal for a container environment because its configuration can be changed with environment variables. Refactoring for cloud native development Refactoring is the process of taking a monolithic application and breaking it down into microservices so it can be rebuilt as a cloud native application. Cloud native development builds and designs a new application based on a microservices architecture. A microservice provides one business capability. Each microservice can be managed separately by a dedicated team member. Microservices can be scaled individually and, when running in Cloud Pak for Applications, can be auto-scaled based on demand. This allows for more agile development and continuous delivery. New services can be developed by leveraging the organization’s set of micro services. Cloud Pak for Applications supports cloud native applications by providing many runtimes for popular programming languages such as Python and Nodejs. © 2020 IBM Corporation IBM IT Economics Consulting & Research Getting started Applications using WebSphere 8 and above can leverage its migration report that details what alternative platforms a WebSphere application may be migrated to, for example, Liberty for Java on IBM Cloud™. Both the Cloud Pak for Applications Transformation Advisor and the WebSphere migration report estimate migration time and complexity. This enables an organization to identify easy-to-move applications as first migration candidates for replatforming or repackaging versus more complex applications that may require a more involved modernization effort. Once the replatforming and repackaging candidates are identified, the process is simple through the use of build and configuration files provided by the Transformation Advisor in Cloud Pak for Applications. Transformation Advisor generates WebSphere Liberty configurations based on the application’s specific dependencies such as JDBC drivers and JNDI data sources. It also generates the necessary artifacts for the application to be deployed using containers. Transformation Advisor uses the Cloud Pak for Applications runtimes, such as WebSphere Liberty with Eclipse MicroProfile support, and the associated container images it provides. Steps to replatform Here are the key steps to replatform a WebSphere application in a container. 1. Download code to create a WebSphere container image 2. Put Installation Manager on a Web server 3. Build Base WebSphere Docker images from download2. 4. Edit Sample Dockerfile to set a WebSphere version and specify app 5. Edit WebSphere config Python code to add App and JNDI database resources 6. Run Docker build to create image 7. Create Deployment YAML file 8. Deploy on Cloud Pak for Apps Replatforming savings To determine how difficult or simple replatforming is, we compared the time it takes to create a business as usual, tradional WebSphere environment in a data center versus the time it takes to put a WebSphere application in a container. IBM testing found that replatforming a WebSphere Application Server in a container using IBM Cloud Pak for 2 Keep in mind that containers are immutable so the WebSphere configuration must be created at build time. Also note that any runtime changes will be lost when the container restarts. © 2020 IBM Corporation IBM IT Economics Consulting & Research Applications takes 36% less time than installing WebSphere Application Server in a compared x86 virtual machine.3 Steps to repackage Here are the key steps to repackage a WebSphere application in a container. 1. Download sample code to create a WebSphere Liberty container image 2. Edit Liberty config file (server.xml) from Transformation Advisor 3. Edit Dockerfile from Transformation Advisor 4. Run Docker build to create image 5. Create Deployment YAML file 6. Deploy on Cloud Pak for Applications Repackaging savings We also measured the time it takes to build a traditional WebSphere application in a virtual machine versus repackaging the application into a WebSphere Liberty container. IBM testing found that repackaging WebSphere Application Server to WebSphere Liberty in a container using IBM Cloud Pak for Applications takes 66% less time than installing WebSphere Application Server in a compared x86 virtual machine.4 CI/CD efficiencies after application deployment Once applications are deployed to Cloud Pak for Applications, the benefits of cloud operations and CI/CD can start to reduce IT operations costs. Automated testing and delivery of incremental changes shorten the time and the cost of testing. A single developer can decrease WebSphere Application Server unit code validation time by 33% when using WebSphere Liberty containers in IBM Cloud Pak for Applications compared to redeploying a WebSphere Application Server Application in a compared x86 virtual machine.5 Microservices also contribute to less test time and cost. Since a microservice component has fewer capabilities it becomes easier to test in isolation, and with a smaller REST interface, there is less to test. This allows features to be rolled out more easily when each service is isolated rather than potentially changing
Load more

Recommended publications
  • IBM Developer for Z/OS Enterprise Edition
    Solution Brief IBM Developer for z/OS Enterprise Edition A comprehensive, robust toolset for developing z/OS applications using DevOps software delivery practices Companies must be agile to respond to market demands. The digital transformation is a continuous process, embracing hybrid cloud and the Application Program Interface (API) economy. To capitalize on opportunities, businesses must modernize existing applications and build new cloud native applications without disrupting services. This transformation is led by software delivery teams employing DevOps practices that include continuous integration and continuous delivery to a shared pipeline. For z/OS Developers, this transformation starts with modern tools that empower them to deliver more, faster, with better quality and agility. IBM Developer for z/OS Enterprise Edition is a modern, robust solution that offers the program analysis, edit, user build, debug, and test capabilities z/OS developers need, plus easy integration with the shared pipeline. The challenge IBM z/OS application development and software delivery teams have unique challenges with applications, tools, and skills. Adoption of agile practices Application modernization “DevOps and agile • Mainframe applications • Applications require development on the platform require frequent updates access to digital services have jumped from the early adopter stage in 2016 to • Development teams must with controlled APIs becoming common among adopt DevOps practices to • The journey to cloud mainframe businesses”1 improve their
    [Show full text]
  • Native Cloud Applications: Why Virtual Machines, Images and Containers Miss the Point!
    Institute of Architecture of Application Systems Native Cloud Applications: Why Virtual Machines, Images and Containers Miss the Point! Frank Leymann, Christoph Fehling, Sebastian Wagner, Johannes Wettinger Institute of Architecture of Application Systems, University of Stuttgart, Germany, [email protected] : @inproceedings{INPROC-2016-19, author = {Frank Leymann, Christoph Fehling, Sebastian Wagner and Johannes Wettinger}, title = {Native Cloud Applications: Why Virtual Machines, Images and Containers Miss the Point!}, booktitle = {Proceedings of the 6th International Conference on Cloud Computing and Service Science (CLOSER 2016)}, year = {2016}, pages = {7-- 15}, publisher = {SciTePress} } These publication and contributions have been presented at CLOSER 2016 http://closer.scitevents.org © 2016 SciTePress. Personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must be obtained from the SciTePress. Native Cloud Applications: Why Virtual Machines, Images and Containers Miss the Point! Frank Leymann, Christoph Fehling, Sebastian Wagner and Johannes Wettinger Institute of Architecture of Application Systems, Universität Stuttgart, Universitätsstraße 38, Stuttgart, Germany {leymann, fehling, wagner, wettinger}@iaas.uni-stuttgart.de Keywords: Cloud Computing, Virtualization, Cloud Migration, SOA, Microservices, Continuous Delivery Abstract: Due to the current hype around cloud computing, the term “native cloud application” becomes increasingly popular. It suggests an application to fully benefit from all the advantages of cloud computing. Many users tend to consider their applications as cloud native if the application is just bundled in a virtual machine image or a container.
    [Show full text]
  • High Performance Computing Toolkit: Installation and Usage Guide | Appendix B
    IBM Parallel Environment Developer Edition High Performance Computing Toolkit Version 2 Release 1 Installation and Usage Guide SC23-7287-00 IBM Parallel Environment Developer Edition High Performance Computing Toolkit Version 2 Release 1 Installation and Usage Guide SC23-7287-00 Note Before using this information and the product it supports, read the information in “Notices” on page 255. This edition applies to version 2, release 1, modification 0 of the IBM Parallel Environment Developer Edition High Performance Computing Toolkit (HPC Toolkit) (product number 5765-PD2) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 2008, 2014. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures ..............vii | Part 3. Using the IBM PE Developer | Edition graphical performance Tables ...............ix || analysis tools ...........21 About this information ........xi | Chapter 6. Using the hpctView Who should read this information .......xi Conventions and terminology used in this || application .............23 information ..............xi || Preparing an application for analysis ......24 Prerequisite and related information ......xii || Working with the application ........25 Parallel Tools Platform component .....xii || Opening the application executable ......25 How to send your comments ........xiii || Instrumenting the application ........28 || Running the instrumented application .....29 Summary of changes ........xv || Viewing performance data .........37 | Chapter 7. Using hardware Limitations and restrictions .....xvii || performance counter profiling.....41 || Preparing an application for profiling......41 Part 1. Introduction .........1 || Instrumenting the application ........41 || Running the instrumented application .....43 Chapter 1. Introduction to the IBM HPC || Viewing hardware performance counter data . 45 Toolkit ...............3 IBM PE Developer Edition components .....3 || Chapter 8.
    [Show full text]
  • Serverless Cloud Computing: a Comparison Between "Function As a Service"
    SERVERLESS CLOUD COMPUTING : A COMPARISON BETWEEN "F UNCTION AS A SERVICE " P LATFORMS Víctor Juan Expósito Jiménez and Herwig Zeiner JOANNEUM RESEARCH Forschungsgesellschaft mbH, Steyrergasse, Graz, Austria ABSTRACT Cloud computing is moving fast and continually progressing. Beyond the microservices architecture, a new paradigm appears to be evolving and complementing it. By using a serverless computing architecture, faster and more reliable developments are possible in several fields such as the Internet of Things, industrial or mobility applications. In this paper, a serverless computing architecture is described and, in addition, a comparison of the most important "Function as a Service" platforms is given. KEYWORDS Serverless Architecture, Function as a Service (FaaS), Cloud Computing, Microservices 1. I NTRODUCTION The Internet of Things (IoT) has changed the way applications are designed. Billions of devices will be connected to the network in a near future. The next generation of connected applications has to change the way they have been designed to support this exponential growth of connected devices and their corresponding services. At the moment, a microservices architecture can fulfill these requirements where the combination of different services is a main issue. In this kind of cloud computing architecture, all tasks and the logic are split in small services, where each is able to serve just one specialized purpose instead of one monolithic component for all purposes. This allows a more versatile development in which maintenance and updates can be done only to the needed components without changing the whole core system. Every service is isolated and all information and all controllers are accessible through external APIs.
    [Show full text]
  • Polycom UC Software 5.4.3 Administrator Guide
    ADMINISTRATOR GUIDE UC Software 5.4.3 | March 2016 | 3725-49104-010A Polycom® UC Software 5.4.3 Copyright© 2016, Polycom, Inc. All rights reserved. No part of this document may be reproduced, translated into another language or format, or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. 6001 America Center Drive San Jose, CA 95002 USA Trademarks Polycom®, the Polycom logo and the names and marks associated with Polycom products are trademarks and/or service marks of Polycom, Inc. and are registered and/or common law marks in the United States and various other countries. All other trademarks are property of their respective owners. No portion hereof may be reproduced or transmitted in any form or by any means, for any purpose other than the recipient's personal use, without the express written permission of Polycom. Disclaimer While Polycom uses reasonable efforts to include accurate and up-to-date information in this document, Polycom makes no warranties or representations as to its accuracy. Polycom assumes no liability or responsibility for any typographical or other errors or omissions in the content of this document. Limitation of Liability Polycom and/or its respective suppliers make no representations about the suitability of the information contained in this document for any purpose. Information is provided "as is" without warranty of any kind and is subject to change without notice. The entire risk arising out of its use remains with the recipient. In no event shall Polycom and/or its respective suppliers be liable for any direct, consequential, incidental, special, punitive or other damages whatsoever (including without limitation, damages for loss of business profits, business interruption, or loss of business information), even if Polycom has been advised of the possibility of such damages.
    [Show full text]
  • Program Directory for IBM Enterprise COBOL for Z/OS
    IBM Program Directory for IBM Enterprise COBOL for z/OS V06.02.00 Program Number 5655-EC6 FMIDs HADB620, JADB621, JADB622, JADB62H for Use with z/OS Document Date: September 2017 GI13-4526-01 Note Before using this information and the product it supports, be sure to read the general information under 7.0, “Notices” on page 30. © Copyright International Business Machines Corporation 1991, 2017. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents 1.0 Introduction . 1 1.1 Enterprise COBOL Description ......................................... 1 1.2 Enterprise COBOL FMIDs ........................................... 4 2.0 Program Materials . 5 2.1 Basic Machine-Readable Material ....................................... 5 2.2 Optional Machine-Readable Material ..................................... 6 2.3 Program Publications . 6 2.3.1 Optional Program Publications ...................................... 7 2.4 Program Source Materials ........................................... 7 2.5 Publications Useful During Installation .................................... 7 3.0 Program Support . 8 3.1 Program Services . 8 3.2 Preventive Service Planning .......................................... 8 3.3 Statement of Support Procedures ....................................... 9 4.0 Program and Service Level Information ................................. 10 4.1 Program Level Information .......................................... 10 4.2 Service Level Information ..........................................
    [Show full text]
  • DB2 Product Overview
    PH061-Martineau.book Page 3 Wednesday, August 6, 2003 7:40 PM C HAPTER 1 DB2 Product Overview he relational database of choice for modern distributed applications is IBM’s DB2 Univer- T sal Database(UDB). Relational databases form the core backend of most enterprise scale applications because of their capability to deliver high performance, support advanced features such as transactions, and maintain data integrity. The Structured Query Language (SQL) provides a powerful standard for accessing and manipulating databases. Its widespread acceptance across all major vendors has also contributed to the success of relational database technology. This chapter introduces major DB2 products so that you can plan the products required for your environment. This is a key to planning the DB2 UDB solution, as shown in Figure 1.1, that is suitable for your project or your organization. OBJECTIVES After reading this chapter you should have an understanding of the following DB2 UDB products: • DB2 UDB Server Products ° DB2 UDB Enterprise Server Edition (ESE) ° DB2 UDB Workgroup Server Edition (WSE) ° DB2 UDB Workgroup Server Unlimited Edition (WSUE) • DB2 UDB Personal Edition (PE) • DB2 UDB Developer’s Products ° DB2 UDB Personal Developer’s Edition ° DB2 UDB Universal Developer’s Edition • DB2 UDB Connect Products ° DB2 UDB Connect Enterprise Edition ° DB2 UDB Connect Unlimited Edition 3 PH061-Martineau.book Page 4 Wednesday, August 6, 2003 7:40 PM 4 Chapter 1 • DB2 Product Overview ° DB2 Connect Personal Edition ° DB2 Connect Application Server Edition • DB2 UDB Clients ° DB2 Run-Time Client ° DB2 Administration Client ° DB2 Application Development Client DB2 UDB SERVER PRODUCTS DB2 UDB server products provide a relational database engine for storing, maintaining, and accessing data.
    [Show full text]
  • File Servers: Is It Time to Say Goodbye? Unstructured Data Is the Fastest-Growing Segment of Data in the Data Center
    File Servers: Is It Time to Say Goodbye? Unstructured data is the fastest-growing segment of data in the data center. A significant portion of data within unstructured data is the data that users create though office productivity and other specialized applications. User data also often represents the bulk of the organization’s intellectual property. Traditionally, user data is stored on either file servers or network-attached storage (NAS) systems, which IT tries to locate solely at a primary data center. Initially, the problem that IT faced with storing unstructured data was keeping up with its growth, which leads to file server or NAS sprawl. Now the problem IT faces in storing file data is that users are no longer located in a single primary headquarters. The distribution of employees exacerbates file server sprawl. It also makes it almost impossible for collaboration on the data between locations. IT has tried various workarounds like routing everyone to a single server via a virtual private network (VPN), which leads to inconsistent connections and unacceptable performance. Users rebel and implement workarounds like consumer file sync and share, which puts corporate data at risk. Organizations are looking to the cloud for alternatives. Still, most cloud solutions are either attempts to harden file sync and share or are Cloud-only NAS implementations that don’t allow for cloud latency. Nasuni A File Services Platform Built for the Cloud Nasuni is a global file system that enables distributed organizations to work together as if they were all in a single office. It leverages the cloud as a primary storage point but integrates on-premises edge appliances, often running as virtual machines, to overcome cloud latency issues.
    [Show full text]
  • IBM Z Open Development Version 1.0: Host Configuration Guide Figures
    IBM Z Open Development Version 1.0 Host Configuration Guide IBM SC27-9297-01 IBM Z Open Development Version 1.0 Host Configuration Guide IBM SC27-9297-01 Note Before using this information, be sure to read the general information under “Notices” on page 27. Second edition (March 2019) This edition applies to IBM Z Open Development Version 1.0 and to all subsequent releases and modifications until otherwise indicated in new editions. IBM welcomes your comments. You can send your comments by mail to the following address: IBM Corporation Attn: Information Development Department 53NA Building 501 P.O. Box 12195 Research Triangle Park NC 27709-2195 USA You can fax your comments to: 1-800-227-5088 (US and Canada) When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright IBM Corporation 2015, 2019. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures ............... v Customization setup ........... 11 PARMLIB changes ............ 12 Tables ............... vii Set the z/OS UNIX definitions in BPXPRMxx .. 12 Product enablement in IFAPRDxx ...... 12 LINKLIST definitions in PROGxx ...... 14 About this document ......... ix Requisite LINKLIST and LPA definitions ... 15 Who should use this document ........ ix PROCLIB changes ............ 16 ELAXF* remote build procedures ...... 16 Host Configuration Guide ...... 1 Security definitions ............ 18 idz.env, the environment configuration file .... 18 Chapter 1. Planning.......... 3 Migration considerations .......... 3 Chapter 3. Other customization tasks 21 Planning considerations .......... 3 z/OS UNIX subprojects .........
    [Show full text]
  • Smart-Cloud: a Framework for Cloud Native Applications Development
    University of Nevada, Reno Smart-Cloud: A Framework for Cloud Native Applications Development A dissertation submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Computer Science and Engineering by Jalal Hasan Ahmed Al Kiswani Dr. Sergiu M. Dascalu/ Dissertation Advisor Dr. Frederick C. Harris, Jr./ Dissertation Co-advisor May, 2019 Copyright © by Jalal Kiswani All Rights Reserved THE GRADUATE SCHOOL We recommend that the dissertation prepared under our supervision by JALAL HASAN AHMED AL KISWANI Entitled Smart-Cloud: A Framework For Rapid Cloud Application Development be accepted in partial fulfillment of the requirements for the degree of DOCTOR OF PHILOSOPHY Dr. Sergiu M. Dascalu, Advisor Dr. Frederick C. Harris, Jr., Co-advisor Dr. Feng Yan, Committee Member Dr. Sage Hiibel, Committee Member Dr. Scotty Strachan, Graduate School Representative David W. Zeh, Ph. D., Dean, Graduate School May, 2019 i Abstract The development of modern software applications requires the adoption of cutting- edge techniques, technologies, frameworks, tools, and infrastructure. Even though there are many options to choose in every category, the common characteristics are faster-delivery, lightweight and scalable applications, and lower cost. In addition, the automation of testing, deployment, and operations have become significant. All of these new characteristics would not be possible without Cloud-Computing, where services are delivered in three different flavors, Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). However, developing high-quality cloud-based software applications that exploit the full benefits of cloud computing is challenging and costly, since it requires a long learning curve and it is challenged by the lack of expertise.
    [Show full text]
  • Valuing Intellectual Capital, Multinationals and Taxhavens Springer Verlag 2013
    Collected References, available on-line as <i.Stanford.edu/VIC/allVICcitations.pdf> 27-Oct-13 References for: Gio Wiederhold: Valuing Intellectual Capital, Multinationals and Taxhavens Springer Verlag 2013 VIC Citations This list includes all the references cited, as well as others that I have persused. For general information, I chose a recent publication for citation, trusting that it will be easier to locate and cite earlier work. As is common in tax matters, opinions abound. Refereed material is italicized. Entries cited and listed in the Reference section of Valuing Intelectual Capital have [bold identifiers]; entries considered, but not cited are marked ‡. Entries marked † were used for [W:06] . Transcription into the spreadsheet for VIC are marked [xls/worksheet]. Shaded text is to be omitted in publication, but helpful for search or as an aide de memoire. I am dding {chapter.section} references AAAAAAA [Aaron:13B] Henry J. Aaron: Tax Reform? Between a Rock and a Hard Place; Huffington Post, Brookings, 15 Jan. 2013. The 1986 reforms shifted $1T (adjusted) from individuals to Corportations over 10 years. Mobility of capital and the proliferation of multinatinal companies prevents such a solution now. Must raise personal income tax.{VIC Ch10.7.4} [Aaron:13G] Henry J. Aaron: You Get What You Pay For: Lessons From the IRS Scandal; Brookings, 31 May 2013. Only 1% of returns is audited. $450B is uncollected. Each dollar spent auditing yields $8. {VIC Ch8,7.3} [AbahoonieA:10]‡ Edward Abahoonie and Liah Alfonso: Deferred taxes on foreign earnings: A road map; Price Waterhouse Coopers (PwC), Dec.2010, updated 2012 www.pwc/us/tax.
    [Show full text]
  • Impact of Implementing Cloud Native Applications in Replacement to On-Premise Applications
    Published by : International Journal of Engineering Research & Technology (IJERT) http://www.ijert.org ISSN: 2278-0181 Vol. 9 Issue 06, June-2020 Impact of Implementing Cloud Native Applications in Replacement to on-Premise Applications A R Sri Nandhini Alaine Joseph Ajay S M.Tech. Software Engineering M.Tech. Software Engineering M.Tech. Software Engineering Vellore Institute of Technology Vellore Institute of Technology Vellore Institute of Technology Chennai, India Chennai, India Chennai, India Abstract — Cloud computing is a well-known worldview to Users spend much money on buying a powerful computing figuring assets. Cloud-native technologies incorporate the unit for their requirements. Instead, we can run the same application system in a dynamic cloud environment, which may applications at a cheaper cost on an online platform. This include private, public, or hybrid. It focuses on activity and methodology also reduces the need for periodic up-gradation agility. This paper speaks about implementing cloud-native of computing components in the users' side. The significant of applications in replacement to on-premise applications. We implement Platform as a Service (PaaS) for Application the cloud-based virtual machine is developing with new Streaming through the premise, rather than incorporating the advancement in virtualization innovation. The gushing of conventional procedure of setting up on-premise application huge estimated virtual machines tends to the issue of software on each system. The paper also tries to provide an restrictive privileges of the product and cost and support insight into the advantages of a native-cloud application over an issues on the customer end. It is not doable to stream on-premise one.
    [Show full text]