CORE COURSE- XI :

23PCA11- CLOUD COMPUTING

Dr. A. Kangaiammal, MCA, M.Phil., M.E., Ph.D.

AP/Computer Applications & Head
Government Arts College(Autonomous)
Salem – 636 007.
 COURSE OBJECTIVES
At the end of this the learners will :
– Understand the current trends and basics of Cloud
computing.
– Know the types of virtualization.
– Understand the role and state of security in Cloud
Computing
– Understand the ways and means to manage
Security in Cloud.
– Explore the Cloud Migration solutions and
challenges
 COURSE OUTCOMES
On successful completion of the course, the
students will be able to:
– Collaborate the cloud services to any device.
– Implement virtualization.
– Explain the role and state of security in Cloud
Computing
– Outline the ways and means to manage Security in
Cloud.
– Connect the Cloud Migration solutions and
challenges
 UNIT V
Migrating Applications to the
CloudComputing: Motivation for Migration – Issues
–Challenges-Solutions for Challenges – Types of
Migration – Planning for Migrating to Applications
to Cloud – Migration Roadmap – Cloud Bursting.
Migration to Microservices – Microservice
Architecture – Benefits – Drawbacks –Checklists for
Migration from Monolithic to Microservices-
Comparison of Microservices with SOA – Google
Cloud Solutions.
REFERENCE BOOKS:
V.K. Pachghare, “Cloud Computing”, PHI, 2012.
 Introduction
• Shifting to cloud computing environment.
• First identify the necessary support required.
• Second, find CSP to support the features of
the applications.
• Spport for data, latencies, hardware support,
storage, etc.
• APIs for services like software services,
infrastructure, and in case of platform
provider, API for applications.
 Motivation for Migration
• Objectives :
– Easily available for most of the users.
– Sy access from anywhere.
– Agility and flexibility
– Availability
– Greater security
– Low cost
– More responsiveness
• The above objectives are satisfied by the
characteristics of characteristics of cloud
computing.
 Motivation for Migration
• On migration, people have following
worries:
– Security
– Control of components
– Integration of host system with cloud
– Applications availability and reliability
– Change of cloud service provider
• Technical and business parameters to be
studied before migration.
 Issues & Challenges in Migrating
the Applications to the Cloud
• Issues:
– OS Compatibility
– Software Availability
– Licensing Activation
– Server Database
• Challenges:
– Data Sensitivity
– Security
– Inter-Operability
– Portability
– Adoptability
– Cost and Duration
– Service Level Agreements
 Solutions for the Challenges in
Cloud Migration
• Concerns:
– Security and cost of migration
– Location of data not know.
– Rules and regulations governed.
• Solutions:
– Use of Encryption
– Data Backups
– Skilled and experienced Technical Personnel
– Security Service Available from Security Service
Providers
 Types of Migration
• Change the various components
• Partially migrate some
functionality
• Migrate the complete stack of
software
• Complete migration of the
application
 Planning for Migrating the
Application to Cloud
• Steps in Planning :
– Identify Reputable CSP
– Selection of application for Cloud Migration
– Identify the risk
– Cost of data transmission
– Identify suitable cloud model for Migration
– Guarantees above services
– Check the legal aspects
 Migration Roadmap
• Steps:
1. Evaluate the applications
2. Develop the business case
3. Design the approach
4. Use an integration model
5. Identify the security and privacy needs
6. Supervise the migration
 Migration Roadmap:
Evaluate the Applications
• Business applications
• Life-cycle of the applications
• Architecture of the applications
• Data
• Technology
• Security
• Application Integration
 Migration Roadmap:
Develop the Business Case
• Cost of Application Migration • Level of service provided
– Cost of on-going cloud – Performance
service – Availability
– Management of service – Regular compliance
– Management of license – Privacy
– Redesigns – Security
– Deployment and Testing of • Business factors
Application – User Requirements
– Maintenance and – User acquisition
administration of
– Revenue
applications
– Costs for handling loads
– Integration
– Time required for delivering
– Training Cost
to market
– Changes in Human Resources
 Migration Roadmap :
Design the Approach

• Platform as a Service Migration

• Infrastructure as a Service Migration
• Technical Considerations
– Skills
– Security
– Integration
– Monitoring and Management
– Scalability
– Availability and Backup
• Patterns
 Migration Roadmap :
Use an Integration Model
• Process Integration
• Data integration
• Presentation Integration
Migration Roadmap :
Identify the Security and Privacy needs

• Which data
• Security Verification of data
• Privacy sensitive data
• Et the regulations
• Conduct risk management
 Migration Roadmap :
Identify the Security and Privacy needs
• Which data
• Security Verification of data
• Privacy sensitive data
• Et the regulations
• Conduct risk management
• Review of Security and Privacy Mechanisms
• Information for various situations
• Cloud services are used by multiple people
• User deprovisioning process without bothering the
Solution authorization and authentication
 Migration Roadmap :
Supervise the Migration

• Procedure for Application Migration:

– before shifting the application to the cloud,
essential to deploy cloud
– Next install and configure application by CSP
– Provide support for the business and strong
security, some more utilities are required
– Take a trial for the execution of the application
migration
– Solve the issues if any.
 Migration Roadmap :
Supervise the Migration

Application Type Cloud Platform

Cloud Native Type SaaS, PaaS, IaaS
E-Commerce, E-Business SaaS, PaaS
Enterprise Application SaaS, IaaS
Disaster Recovery IaaS
Business Applications SaaS
Batch Computing PaaS
Testing and Development IaaS
 Cloud Bursting
• Application Deployment Model
• Application runs in an on-premise infrastructure
or on a private cloud
• Method of using one or more public cloud
services to handle extra spikes.
• Concerns for Cloud Bursting:
– Type of services running in data-centre
– Privacy and Security on transmission and migration
– Better performance in terms of agility, speed and scaling
– In peak of demand – effective load balancing
– Challenges about latency
– If in hybrid –cloud, then there should be inter-operability
 Cloud Bursting
• Benefits of Cloud Bursting:
– Supports for enlarging and withdrawing of services
as per capacity requirements
– Reduces the cost
– Performance improvement with spikes in workload
– Bursting new occurrence of applications with other
cloud
– Supports to burst scalable application
– Capital expenses are reduced.
– In Hybrid: Recovery in case of disaster or failure
– In Hybrid: Availability increased
 Cloud Bursting
• Challenges of Cloud Bursting:
– Configuration and Management of more than one
clouds
– Latency
– Security
• Disaster Recovery using Hybrid Cloud:
– More flexible
– Cost-effective
– Alertness
 Cloud Bursting
• Challenges of Cloud Bursting:
– Configuration and Management of more than one
clouds
– Latency
– Security
Migration to Microservices
 Microservices
• Microservices to update frequently in a day, easy-to-
execute on cloud platform.
• Multiple services which can be deployed independently.
• These services focuses on a narrow part of the
applications.
• Scalability and agility is provided.
• Working depends on the capability to roll up the
services in different containers.
• Major tool in the architecture.
• More choices and options for evolving the service.
• Process of development in mobile and web applications.
 Need of Microservices
• Monolithic Applications
– Single code for all components of an
application.
– System to have browsers – HTML, CSS,
JavaScript.
– Long code, difficult to understand.
– Integration and deployment is tough.
– IDE may be overloaded and affects build time.
– Components are tightly coupled; difficult to
change the language, framework or technology.
 Need of Microservices
• Challenges with Monolithic Applications
– Emergence of new technology
– Uninterrupted Release
– Scaling Problem
– Many Teams
– Addition of new members
• Microservices Applications:
– Laptop/Desktop-based is transited to mobile-based
applications.
– Changing back-end architecture
– Application with group of several small services written in
various languages.
 Need of Microservices
• Characteristics of Microservices:
– Autonomous
– Modelled around the Business Domain
– Size
– Standalone
– Easy Integration
 Need of Microservices
• Attributes of Microservices:
– Componentization as a service
– Organized around business capabilities
– Development based on products
– Smart endpoints and dumb pipes
– Decentralized Control
– Data Management decentralization
– Automation of infrastructure
– Recovery from failure
 Migration to Microservices
• It is essential to investigate multiple design features.
• Benefits and Drawbacks:
– Divide the Monolith
– Communication between two Services
– Testing
– Deployment
– Failure Isolation – 100% not successful
– Service Discovery – DNS cannot scale dynamically
– Monitoring – Splunk and LogStash for logging
– Documentation – no understanding, not at all used
– API Gateway – offers method to handle issues related to
security, transformation, authentication, load-balancing,
dependency resolution and request dispatching.
 Microservices Architecture
Monolithic Architecture

Browser
Load Balancer
Monolithic Component Component
Application 1 2

Relational Component Component Component

Database 3 4 5

Component
6
Microservices Architecture
Benefits of Microservices
• Code is Small and Easy to Understand
• Easy to Scale
• Smaller Teams
• Easy to Throw Away
• Easy to Deploy
• Capability to Employ Diverse Technology
• System Resilience
Drawbacks of Microservices
• Communication Overhead
• Documentation Overhead
• Diverse Application
• Maintenance Complexity
• More initial investment
• Enlarge Communication
• Gathering the Data
• Security
• Testing
• More Monitoring Cost
Checklists for Migration from
Monolithic to Microservices
Checklist-1- Loosed coupled for modification
• Change in technology-time consuming – hence avoided
• Continuous integration – more deployment time –
delayed.
• Design change needs coordinator of teams -
Evolutionary changes are deferred.
• Change of Team- more time required
• Implementing change amidst teams – tough
• Failure in one component –all down.
• Cloud means, high operational cost – high complexity.

• Therefore, Need of tightly-coupled modular

architecture to avoid downtime of system failures.
Checklist-2 – Movement to Microservices
• Begin with small number of coarse grained but self-
contained services.
• Number of moving parts in micro services.
• Members of team need time to cope with this new
application.
• Service composition of team based on technology, self-
contained features with less shared functionalities.
• Tools like log aggregation, application metrics, system and
log dashboard, automated deployment and granular
monitoring should be mandatorily added to the stack.
• Different team structure for monolithic and Microservices
architecture.
• Standardized service templates required.
• Monolithic co-exist with Microservices for sometime.
Checklist-3- Secured Migration with co-existence
• Add features required to be added instead of going in
Microservices.
• Decide a standard interface to co-exist b/w both
monolithic and microservices.
• Set up own runtime environment and isolated
infrastructure.
• Team for development, operation and maintenance of
the new application.
• Multiple versions of the same feature for supporting
both together.
• New service template.
• Build coarse-grained services than fine-grained
services.
 Checklist-4: Challenges with Migration
• Services need proper documentations of
active services and their specific versions.
• No longer needed services to be handled
properly.
• Integration testing after any update in
microservices.
• Identify proper size, not too small or large.
• Rewrite or partition the existing services if
needed.
 Comparison of Microservices with SOA
Traditional SOA Microservices
Messaging Smart Dumb, Fast Messaging
Size of code 100s or 1000s of lines 100 or fewer lines of code
per service
State Stateful Stateless
Communication Synchronous Asynchronous
Databases Relational NoSQL or Micro SQL
Type of coding Procedural Functional
Evolution Big Services Evolve Small services are Immutable and may be
discarded or ignored
Systematic Modify Monolith Create a new Service
Change
Scaling Optimize the System Powerful Services are added
System Level Less aware, Event More aware, Event-driven
Awareness driven
 Google Cloud Solutions
• x
Thank you