service virtualization 101
DESCRIPTION
Ever sit in a meeting and hear “I can't get my job done because ‘Chris’ is not done with the code I need to develop my code”? This is the content from an education session enabling attendees to learn about Service Virtualization and find out which problems it solves and how it differs from developers stubbing and mocking. It describes the differences between virtualizing hardware and hypervisors vs. simulating business behavior and services. Presentation by Chris KrausTRANSCRIPT
Service Virtualization 101: What is a Virtual Service and What Is Not
Chris Kraus
DCX12E
CA TechnologiesSenior Principal Product Manager
ca DevCenter
3 © 2014 CA. ALL RIGHTS RESERVED.
Agenda
TYPES OF VIRTUALIZATION
HOW IS SERVICE VIRTUALIZATION DIFFERENT?
DEMONSTRATION
1
2
3
Types of Virtualization
5 © 2014 CA. ALL RIGHTS RESERVED.
Introduction: What is Virtualization?
Leading technology analysts broadly define virtualization as “the practice of simulating the behavior of a physical asset.”
For example, a server or application in a software emulator then hosting that emulator in a virtual environment
The virtual environment must behave enough like the physical environment to ensure interactions with the emulated service look like the real one.
Benefits of virtualization include:
Control: Better ability to manage physical assets, simplifying change and configuration management
Capacity: Improved utilization of physical assets
Agility: Reduced wait time (and associated costs) related to IT groups making changes to environment configurations and hardware resource allocations
6 © 2014 CA. ALL RIGHTS RESERVED.
Virtualization Types
Virtualization is the creation of a virtual (rather than actual) version of an asset, such as:
Operating systems
Servers
Storage Devices
Network Resources
Data Services
Virtualization examples:
VM Ware
Citrix
VPN
and others . . .
7 © 2014 CA. ALL RIGHTS RESERVED.
SDLC ChallengesWithout Virtualization in Use
INTEGRATION LAYER
Application 1 Application 2
Service 2Service 1
MFSaaS or Hosted
Solution
Net effect of these issues:
Server proliferation
Lost productivity in development
Greater cost of third-party systems
Increased risk of production issues
Cloud/SaaS issues:1. Costly access2. Volatile data
App team issues:1. Every App team needs their
own infrastructure.2. Every discipline (Dev, Test, Int)
wants their own environment.
Server issues:1. Access restricted2. Capacity constraints3. Data volatility4. Security concerns
Service provider issues:1. Commingled services2. Difficulties with parallel
development of apps and services
8 © 2014 CA. ALL RIGHTS RESERVED.
Hardware Virtualization
Hardware virtualization is the simulation of hardware behavior.
The key driver of hardware virtualization is to improve utilization of physical capacity.
Can be used to:
Virtualize test beds.
Maintain the countless configuration of operating systems and platforms that software needs to run against.
Some limitations include:
Many of the enterprises most complex (mainframes) and costly systems (externally hosted partner services, SaaS, cloud-based systems and systems under a high degree of change) can not be imaged into a virtual machine.
It does not adequately address non-hardware costs, such as licensing, data volatility, patch release managementand other significant IT admin costs (maintaining server images, software configurations, installs, etc.).
It cannot contain cost and stabilize the data of third-party hosted applications, SaaS and cloud-based systems.
9 © 2014 CA. ALL RIGHTS RESERVED.
Hardware virtualization is helpful... but still NOT enough.
Application Application
MFSaaS or Hosted
Solution
Net effect:
Middle-tier server proliferation prevented
Largest, most complex, most costly systems not affected
Cloud/SaaS issues UNCHANGED:1. Costly access2. Data volatility
App team issues HELPED:1. First level of connectivity solved
App team issues UNCHANGED:1. Back end systems/services
Server issues UNCHANGED:1. Restricted access2. Capacity constraints3. Data volatility4. Security concerns
Service provider issues HELPED:1. Commingled services SOLVED2. Difficulties with parallel
development of Apps and Services
Vir
tual
Ser
ver
How Is Service Virtualization Different?
11 © 2014 CA. ALL RIGHTS RESERVED.
Added Value Through Service Virtualization
[virtualized within VSE]
App team BENEFITS:1. All teams get their own extended
environment at very low incremental cost.
2. There are no conflicts with other application teams
Server BENEFITS:1. Available 24/72. Unlimited capacity3. Data consistency4. Sensitized for security
Service provider BENEFITS:1. Services all in isolated
environment2. Virtual services enable parallel
development.
Virtual Service Environment
Virtual Servers
Service2vsMFvs
Hardware Virtualized VM instance
Integration Layer
Service2vs
12 © 2014 CA. ALL RIGHTS RESERVED.
CA Service Virtualization
Service virtualization involves the modeling of a virtual service process and the imaging of software service behavior to “stand in” for the actual service during development and testing.
Is complementary to hardware virtualization and provides a solution to address hardware virtualization limitations
CA has developed the ability to virtualize the behavior of applications and infrastructure components at either the entire endpoint or at an interface level. This enables organizations to:
Provide 24/7 access to service end points
Remove capacity constraints
Remove contention for shared resources
Provide an alternative to unavailable systems and those still under development
Control complex data scenarios that are inherent during the SDLC
Reduce or eliminate the cost of invoking third-party systems for non-production use
13 © 2014 CA. ALL RIGHTS RESERVED.
The function of a “virtual service” can be summarized in three steps:
The behavior of the “process” step can be a variety of actions:
Perform some business logic:
‒ Deactivate expired accounts
‒ Send emails to customers
‒ Print weekly reports
Retrieve the correct ZIP code for a supplied address
Retrieve rows from a database to include in the response
Add/update/delete rows from a database
What does a “Virtual Service” do?
RESPONDPROCESSLISTEN
14 © 2014 CA. ALL RIGHTS RESERVED.
Assumptions About Virtual Services
The virtual service (VS) created by CA Service Virtualization will stand in for the real service
We are not duplicating all of the real service’s complex logic
Assumptions include:
VS can predict future behavior from current behavior: Behavior is fully encompassed in request/response loops (VSE txns)
Variation in responses are based on either the input value variation and/or the context of the conversation
VS can lie and consumers won’t know or care, however: The structure of the response must be what they expect
Consumers will verify that values they provide as input match output, otherwise they will get upset
Dates being outside of their expectations really make the consumer upset
15 © 2014 CA. ALL RIGHTS RESERVED.
The Big Problem: Constraints Across the SDLC
“I can’t do anything until I have everything…and I never have everything!”
ESB
!
!
! ! !
System Unavailable
x x x
x
Invalid data Access Fees
Incomplete Development
16 © 2014 CA. ALL RIGHTS RESERVED.
The Big Problem: Constraints
“I have everything I need, when I need it!"
ESB
! ! !
System Unavailable Invalid data Access Fees
Incomplete Development
17 © 2014 CA. ALL RIGHTS RESERVED.
CA Enables True Agile Development
PRESENTATION
APPLICATION SERVICES
INTEGRATION LAYER
BACKEND
ESB
CA Application Test
18 © 2014 CA. ALL RIGHTS RESERVED.
Living, breathing “live” model
Sophisticated, contextual behavior
Automatic handling for dynamic properties
Service Virtualization: How does it work?TRUE AGILE
DEVELOPMENT
CAPTURE PROCESS MODEL
Record traffic between existing systems.
Create from engineering specifications.
Draw from sources such as log files, sample data, packet capture and CA Continuous Application Insight.
19 © 2014 CA. ALL RIGHTS RESERVED.
DevTest Benefits
Provide round-the-clock access to service end points.
Remove capacity constraints.
Remove contention for shared resources.
Provide an alternative to unavailable systems and those that are still under development.
Control complex data scenarios that are inherent during the SDLC.
Reduce or eliminate the cost of invoking third-party systems for non-production use.
Increase agility and improve quality in complex and changing IT environments.
Demonstration
21 © 2014 CA. ALL RIGHTS RESERVED.
Devcenter
CA Application Test
DevOps
Agile Parallel Development
Related Technologies
Devcenter
CA Service Virtualization
Devcenter
DevTest Overview
1:15 Monday
22 © 2014 CA. ALL RIGHTS RESERVED.
Q & A
23 © 2014 CA. ALL RIGHTS RESERVED.
Session Evaluation
Please provide your feedback about this session
Session Name:Service Virtualization: What is a Virtual Service and What Is Not
Access inside the CA World Mobile App
Click on SURVEY/SESSION EVALUATION If your badge was scanned at the entrance to
this session, click on the name of this session.
24 © 2014 CA. ALL RIGHTS RESERVED.
For Informational Purposes Only
© 2014 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.
This presentation provided at CA World 2014 is intended for information purposes only and does not form any type of warranty.Some of the specific slides with customer references relate to customer's specific use and experience of CA products and solutions so actual results may vary.
Terms of this Presentation
Copyright © 2014 CA. All rights reserved. All trademarks, trade names, service marks and logos referenced herein belongto their respective companies. CA confidential and proprietary. No unauthorized copying or distribution permitted.