Top 5 benefits of transforming your dev environment on cloud

US | UK | BENELUX | ME | IND©1996-2016 Aspire Systems, Inc.

Contents

Complexities introduced by agile practices

Agile Needs

Scenarios suitable for DevFarm VDI Fitment for Development Workload

What is DevFarm?

DevFarm implementation architecture in AWS

DevFarm Cost benefits and TCO comparison between on-premises and Cloud infrastructure

1

2

3

4

5

6

Part #1

Part #2


Complexities Introduced by Agile Practices

Faster Turnaround

More Dependencies

Increased Coordination

Multi Level Collaboration

Consistency across teams


Disconnect between IT and Development

IT and Developers often lack common ground

Developers

IT

ControlVisibility

Compliance

AgilityProductivity

Time to Market


Dev vs. IT

Development Team

Need IT

5 New Contractors are joining next week to meet the new

timelines promised to customers.

Decided to follow a Feature Based Development model.

Developers need to work in parallel on multiple projects

Support teams need access to multiple versions

Geographically distributed teams working in parallel

5 new workstations with all software setup in less than a

week

Multiple development environments in parallel

Multiple environments for each developer

Separate environment has to be maintained for each version

Shared dev environments to work collaboratively

Need more time

No budget

No space

No IT Support bandwidth

Can’t allow – Security issues


Agile Needs

The development environments (as a stack) should be available on-demand at the disposal of developers

Team should have self-servicing capability to create their (multiple) development environments without any intervention from IT teams

Each team should be able to make progress without any dependency with other development teams

Teams should be able to easily share/access common environments, easing the collaboration efforts

Templated environments should be used across the teams for ensuring consistency


Virtual Desktop Infrastructure (VDI)

Centralized Management of Desktops Efficient power consumption Access anywhere, anytime Secure


VDI Fitment for Development Workload

Typical Desktops

Development

Environments

VDI Solutions mostly applicable for vanilla workstations/desktops

Desktops typically contain standard set of software

Software configurations don’t change oftenOffers excellent options for managing the desktops but less support on the desktop customization

Not designed for sharing of desktops

Follows a workflow for approval and provisioning of desktop

Dev. Environments are typically complex in nature and has interdependenciesWide range of tools might be required depending on the technology stack

Frequent changes in versions of the tools/libraries used in development

Requires medium/heavy customization of the desktop to support the dev technology stack

Most often will require sharing with other developers for co-development

Needs self-servicing capabilities to launch/terminate at will


What is DevFarm?

Deploys Cloud automation for addressing development environment related complexities

Extends VDI Solution to meet the needs of Development environment

Implemented on cloud for cost savings; no CapEx

Offers Self-Service portal to developers, along with the access control to IT

Supports custom rules for usage, configuration, cost limits, etc.

Monitoring dashboards and automated alerts to keep the budgets under control

What is DevFarm

?


Scenario #1

Scenarios Suitable for DevFarm

Companies that deal with multiple parallel releases within a single application. In this case, each team can have it’s own dev environment without affecting other tracks.

Development Testing Teams Releases

Timeline

T1

T2

T3

T4

R1

R2

R3

R4

Application


Scenario #2Leverage a task based approach for developers. Developers can handle multiple tasks across different dev environments. This allows Companies to move away from “effort per release” to “effort task per release”


Dev Env1 Dev Env2 Report Env Tasks

T1 T3

App1

App2

T1

T2

T3

T4


Scenario #3

Stg

IM

IMQA

M2

QA2

Companies that deal with multiple applications release. Each teams can be working on different dev environments. Workload of IT gets drastically reduced in these cases.


App2

App Suite 1

M1

QA1

Dev Int QA Stg


Scenario #4

In Support, where multiple older versions of the products have to be maintained. Developers can fire up the version of dev environment to be worked, complete the work (bug fix, etc.) and remove the environment. This approach tremendously increases the productivity of support teams.


Application Versions

T1 T3T1

T2

T3

T4

X

X

X

X



Cross team working – where you need the flexibility to have the developers work on multiple projects. Instead of providing them 3-4 laptops/desktops – you can simply provide them access to as many environments as required.

Scenario #5

T1

App1 Env App2 Env App3 Env App4 Env

T3 T4T2

LOREM IPSUMPart II


DevFarm – Working Model

Pre-Created Images

DevFarm Admin

Create Environment

Team #1

Team #2

Team #n

Monitoring & Image Management

Sets up the images with the baseline

software to be used by all devs

Devs can launch the

environment at their own will

Completely Automates the environment setup as

well as app related configurations

Support team monitors for

resource usage, cost & image updates

Independent stacks for each team


Developer Control

AWS Service Catalog - Overview

IT Control

Service Catalog

Portfolio

Product

Versions

Stacks


Portfolio Creation


Product Creation – Step 1


Product View


Product – Additional Settings


Developer - Launching a New Stack


Service Catalog – Product Listing


DevFarm Architecture

Creates portfolio 1

2

4

8

3

7

8

6

5

Administrator

Create custom services and grant access

Users

Events

Use a personalized portal to find and launch services

Creates product

Authors template

Adds constraints and

grant accessAWS Cloud Formation template

Dev Env Product

Portfolio

Deploys stacks Events

LaunchProducts

Browse Products

AWS


TCO Analysis


TCO Analysis

3 Years Cost Breakdown

88% yearly savings3 year total savings of $164,657


TCO Analysis

On-Premise AWS


TCO Comparison

25 50 75 100 150 200 $-

$50,000

$100,000

$150,000

$200,000

$250,000

$300,000

$350,000

$400,000

$450,000

$500,000

$187,276

$220,969 $252,863

$286,557

$352,144

$446,306

$22,619 $45,033 $67,399 $89,765 $134,498

$179,231

$164,657 $175,936 $185,464 $196,792 $217,646

$267,075

On-premise AWS Diff CostNumber of VMs

On-premise vs. AWS: 1vCPU, 4GB RAM, 100GB Storage


TCO Comparison

25 50 75 100 150 200 $-

$100,000

$200,000

$300,000

$400,000

$500,000

$600,000

$700,000

$800,000

$214,049

$274,517

$333,184

$420,426

$539,560

$760,077

$42,525 $84,749

$126,974 $169,198

$253,228 $321,242

$171,524 $189,768 $206,210 $251,228

$286,332

$438,835

On-premise AWS Diff Cost

Number of VMs

On-premise vs. AWS: 2vCPU, 8GB RAM, 100GB Storage


TCO Calculator by AWS

https://awstcocalculator.com



Global technology services firm with core DNA of Software Engineering

Specific areas of expertise around Software Engineering, Digital Services, Testing and Infrastructure & Application SupportVertical focus among Independent Software Vendors and Retail, Distribution & Consumer Products1500+ employees; 120+ active customers

CMMI Maturity Level 3, ISO 9001:2008 and ISO 27001 : 2005 certifiedInternational headquarters in Singapore with presence across US, UK, Benelux, Middle East and IndiaRecognized 7 consecutive times as “Best Place to Work for” by GPW Institute

About Aspire


Contact Us

Contact UsWeb : http://www.aspiresys.com/ General Enquiry :

[email protected]

For detailed information:WATCH THE WEBCAST

http://www.aspiresys.com/

http://www.aspiresys.com/

mailto:[email protected]

http://cloud.aspiresys.com/transform-your-development-infrastructure-on-cloud/

LOREM IPSUMThank you

Top 5 benefits of transforming your dev environment on cloud

Technology

Transcript of Top 5 benefits of transforming your dev environment on cloud