enabling mobility through continuous delivery

1© Connecta - Confidential

Enabling mobilitythrough Continuous Delivery

Connecta

Stockholm, 2013-11-20


DEVELOPER

CONTINUOUS

MICHAEL MEDIN

delivery

OUTSIDE THE BOX


Platinum

Gold

Silver

Remarketer

2009

2010

2011

2012Fusion MiddleWare:Partner of the year

2012 2013

Fusion MiddleWare:Most Certified

Implementation Specialists

Speaker and Keynote at many Conferences and

Partner Events


Service Oriented Architecture

Application Integration Architecture

WebLogic/Application Grid

Siebel CRMCRM On Demand

http://www.sonyericssonmobile.com/

http://www.sonyericssonmobile.com/

http://www.vattenfall.se/

http://www.vattenfall.se/


Matts Jöhncke

ICA ABInfrastructure Services

Team lead - development

Configuration manager


MOBILE


MOBILEIs here

Time To MarketCompetition

InternetOut-sourced


MOBILEIs here

Will happen to YOU

Be Prepared

10x traffic


MOBILEAgility is key

Time To Market

Be Prepared

No time to think


MOBILEPrestige projects

Competition

Key stakeholders

Be Prepared


MOBILE

Security nightmare

Internet

24x7 uptime

Be Prepared


MOBILENew technology

Outsourced

New requirements

Be Prepared


Your mission:Cloud provider…

…in 3o days……tomorrow

No won’t be an optionBe Prepared


ArchitectureSOA CloudRest Mobile


Mobile Enablement

SERVICE VIRTUALIZATION & MEDIATION

MAINFRAME

Oracle API GatewayOracle Service Bus

MobileDesktop CloudWeb Servers B2B

access management

security

restAPIservicesoap Web-


What’s behind the box?

SERVICE VIRTUALIZATION & MEDIATION

MAINFRAME

Oracle API GatewayOracle Service Bus

MobileDesktop CloudWeb Servers B2B

API GW

Service bus

SOA BPM AIA ???

Re

po

sitory

Se

curity

DMZ, Security, Control

Virtualization, Versioning, Transformation

Services, Composite Applications

Co

mm

on

Se

curity

Fram

ew

ork

Re

use

, Go

ve

rna

nce


DELIVERYCONTINUOUS

THEORY


1990: Classic software development

Gather Requirements

Write SpecificationBuild

softwareTest software

Deliver Software

Acceptance Test

Done


2000: Iterative projects

Gather Requirements

Write Specification

Build softwareTest software

Deliver Software

Acceptance Test


2000: Modularized architecture

Frontend

Business logic

Backend


2000: Agile projects not code

Gather Requirements

Write Specification

Build softwareTest software

Deliver Software

Acceptance Test


2000: Waterfall Waterfalls

Frontend

Business logic

Backend


INTEGRATIONCONTINUOUS


CONTINUOUSINTEGRATION


Continuous Integration

Code

IntegrateBuild

Test


2010: Enterprise Development

Code

IntegrateBuild

Test Code

IntegrateBuild

Test

Code

IntegrateBuild

TestCode

IntegrateBuild

Test

Mobile Integration

ERPCRM


2020: Agile Enterprise Software development

Code

IntegrateBuild

Test

Code

IntegrateBuild

Test

Mobile

ERP

Code

IntegrateBuild

Test

Code

IntegrateBuild

Test

CRM

Code

IntegrateBuild

Test

Integration


DELIVERYCONTINUOUS


Continuous Delivery

Code

Integrate

Build

Unit-test

Deploy

Acceptance/Integration

test

Release


How about mobility?

Mobile client

Oracle API GW

Service bus

SOA

System A System B

Code

IntegrateBuild

Test

Code

IntegrateBuild

Test

Code

IntegrateBuild

Test

Code

IntegrateBuild

Test

Code

IntegrateBuild

TestCode

IntegrateBuild

Test


DELIVERYCONTINUOUS

PRACTICE


AUTOMATE

Code

Test

Release

InstallConfiguration

DeployAcc. Test Migration

Everything


PIPELINE

DEPLOY

WORKFLOW


ORACLE

WLST ANT

Maven Templates

Silent Installers

(Maven)


DELIVERY

CONTINUOUS

COST


FREEPays it self

There is a free lunch!


Accumulated cost for delivery

0

20

40

60

80

100

120

140

1 2 3 4 5 6

Automated Manual


Project cost after implementing Continuous Delivery

0

50

100

150

200

250

300

350

400

Project A Project B Project C Project D Project E

Ho

urs


Practice Build management and

CI

Environments and

deployment

Release

management

Testing Data management Configuration

Management

Level 3 –

Optimizing: Focus

on process

improvement

Teams regularly meet to

discuss integration problems

and resolve them with

automation, faster feedback,

and better visibility

All environments

managed effectively.

Provisioning fully

automated. Virtualization

used if applicable.

Operations and delivery

teams regularly collaborate

to manage risks and reduce

cycle time.

Production rollbacks

rare. Defects found and

fixed immediately.

Release to release

feedback loop of database

performance and

deployment process

Regular validation that CM

policy supports effective

collaboration, rapid

development, and auditable

change management

processes.

Level 2 –

Quantitatively

managed:

Process measured

and controlled

Build metrics gathered, made

visible, and acted on. Build s

are not left broken.

Orchestrated

deployments managed.

Release and rollback

processes tested.

Environment and

application health monitored

and proactively managed.

Cycle time monitored.

Quality metrics and

trends tracked. Non

functional requirements

defined and measured.

Database upgrades and

rollbacks tested with every

deployment. Database

performance monitored

and optimized.

Developers check in to

mainlined at least once a

day. Branching only used

for releases.

Level 1 – Consistent

Automated

processes applied

across whole

application lifecycle

Automated build and test cycle

very time a change is

committed. Dependencies

managed, Re-use of scripts

and tools.

Fully automated, self-

service push-button

process for deploying

software. Same process

to deploy to every

environment.

Change management and

approvals processes

defined and enforced.

Regulatory and compliance

conditions met.

Automated unit and

acceptance tests, the

latter written with

testers. Testing part of

development process.

Database changes

performed automatically

as part of deployment

process.

Libraries and dependencies

managed. Version control

usage policies determined

by change management

process.

Level 0 –

Repeatable:

Process

documented and

partly automated

Regular automated build and

testing. Any build can be re-

created from source control

using automated process.

Automated deployment to

some environments.

Creation of new

environments is cheap.

All configuration

externalized / versioned

Painful and infrequent, but

reliable, releases. Limited

traceability from

requirements to release.

Automated tests written

as part of story

development.

Changes to databases

done with automated

scripts versioned with

application.

Version control in use for

everything required to

recreate software: source

code, configuration, build

and deploy scripts, data

migrations.

Level -1 –

Regressive

Processes

unrepeatable, poorly

controlled, and

reactive

Manual process for building

software. No management of

artifacts and reports.

Manual process for

deploying software.

Environment-specific

binaries. Environments

provisioned manually

Infrequent and unreliable

releases.

Manual testing after

development.

Data migration

unversioned and

performed manually.

Version control either not

used, or check-in happens

infrequently.

Capability Maturity ModelLevel 1Consistent

Automated

processes applied

across whole



very time a change is committed.

Dependencies managed, Re-use

of scripts and tools.


service push-button


software. Same process to

deploy to every

environment.

Level 0Repeatable:

Process

documented and

partly automated



created from source control using

automated process.


some environments.

Creation of new

environments is cheap. All

configuration externalized /

versioned

Level -1Regressive

Processes

unrepeatable,

poorly controlled,

and reactive




Manual process for

deploying software.




Level 1Consistent

Automated

processes applied

across whole



very time a change is committed.

Dependencies managed, Re-use

of scripts and tools.


service push-button


software. Same process to

deploy to every

environment.

Level 0Repeatable:

Process

documented and

partly automated



created from source control using

automated process.


some environments.

Creation of new

environments is cheap. All

configuration externalized /

versioned

Level -1Regressive

Processes

unrepeatable,

poorly controlled,

and reactive




Manual process for

deploying software.





THE JOURNEY


Fusion

2011: The beginning of a long integration journey

Oracle

Middleware

ODIAIA File

OSB

OAG

OERHarvester


ChallengesVersion “control”Ill suited

Race conditions

AIAWorkbench

Process

DependenciesPoint-to-point

NorwaySweden Finland India

Expertise


FLOWNOT PRODUCT

PROCESS


DELIVERYCONTINUOUS

BENEFITS


AgilityTime To Market

Iterative

Stressincreased

reduced

development

free

Qualityincreased


THROUGHMOBILITYENABLING

DELIVERYCONTINUOUS


Time

MoneyQuality

AUTOMATESAVE

MONEY

SAVETIME

INCREASEQUALITY


Time

MoneyQuality

YES WE CAN


Be PreparedFOR MOBILE


THANK YOU


Our job is to automatebusiness processes.

Why do we do this

manually?

enabling mobility through continuous delivery

Technology

connecta confidentialwhats

agile projects

o daystomorrowno wont

cloud providerin

marketbe preparedno