agile soa: application development in the new enterprise

www.outsystems.com 1 © 2010 OutSystems – all rights reserved

Agile SOA:Application development in the new enterprise

24 May 2010

Paulo Rosado


Traditional


Analysis

Design

Development

Testing

3-6 months 6-12 months

10x – 50xmore expensive

$1

http://images.google.com/imgres?imgurl=http://orangecow.org/pythonet/fang.gif&imgrefurl=http://orangecow.org/pythonet/the-spanish-inquisition.html&h=120&w=162&sz=10&hl=en&start=1&um=1&tbnid=fQ4_4_g5xAV90M:&tbnh=73&tbnw=98&prev=/images?q=horrified+face&svnum=10&um=1&hl=en&safe=off&rls=com.microsoft:en-us:IE-SearchBox&rlz=1I7GFRC


Agile works better


Agile Do things incrementally

Involve the business continuously

Release, asap


2 weeks 2 weeks 2 weeks 2 weeks 2 weeks$1 3x – 5x

Agile MethodologiesProjects are delivered incrementally. Software gets

corrected constantly based on Business Users feedback.

http://images.google.com/imgres?imgurl=http://blogs.eastvalleytribune.com/resserver.php?blogId=19&resource=TRLtyrac.jpg&imgrefurl=http://blogs.eastvalleytribune.com/view.php?op=Default&postCategoryId=33&blogId=19&h=238&w=317&sz=27&hl=en&start=10&um=1&tbnid=uLYY-oleWF9yTM:&tbnh=89&tbnw=118&prev=/images?q=tyra+banks+smiling&svnum=10&um=1&hl=en&safe=off&rls=com.microsoft:en-us:IE-SearchBox&rlz=1I7GFRC


Less software“45% of features will never be

used. I wish I knew which ones”

Features and Functions Used in a Typical System

Never45%

Rarely19%

Sometimes16%

Always7%

Often13%


Functional softwareExactly what is needed.


Reprioritize features for next sprint


Flexible softwareAligned with Business

Changes


Adopted softwareFlexibility is extended into

roll-out phases


Tune application

after launch


IT becomes a Strategic asset… instead of a cost center


Agile is hard


“don’t ever mention that again around here […]

agile is a banned word in this organization”


People

Processagile

ArchitectureSOA

Tools + infrastructur

e


SOA

Break software in state full components

Connect loosely

Use one common protocol


ExampleCustomer Portal


Existing systems

ProductCatalog(custom

build)

OrderManagement

(ERP)

Customer Portal


SOA architecture


build)

OrderManagement

(ERP)

Show Products

ProductService

front-endcomposite

back-endcomposite

orservice


Different SLAsCache data in the service, periodically

9 to 5Order

Management(ERP)

Show Products

Product Service

ProductsCache

24 by 7


Different SLAsService needs to scale

OrderManagement

(ERP)

Show Products

Product Service

ProductsCache

500 requests/sec

10 trans/sec


New data neededNot possible to add it to legacy Master of

Records

OrderManagement

(ERP)

Show Products

Product Service

ProductsCache Too much

change. Not

possible!

PhotosDescriptions


New data needs managementBackoffice of the Portal?

Too much change. Not

possible!

OrderManagement

(ERP)

Show Products

Product Service

ProductsCache

Online Product Mngmt

PhotosDescriptions


SOA architectureInside the Service?


possible!

OrderManagement

(ERP)

Show Products

Product Service

ProductsCache


PhotosDescriptions


SOA frameworkMust-have capabilities


possible!

OrderManagement

(ERP)

Show Products

Product Service

ProductsCache


PhotosDescriptions

• WS protocols• Logic • Scalable• Integration• Database• Scheduling• …and more.


Front-End Composites frameworksObvious capabilities - mashups


build)

OrderManagement

(ERP)

Customer Portal

ProductService

• Web 2.0• Logic• WS protocols• Scalable• …and more.


New data keeps pilling upNot obvious it should be added to a Service


build)

OrderManagement

(ERP)

Customer Portal

ProductService

Wish List

CustomerTracking


Workflows & notifications


build)

OrderManagement

(ERP)

Customer Portal

OrderService

Emails w/ order updates


Front-End Composite frameworksExtra capabilities


build)

OrderManagement

(ERP)

Customer Portal

ProductService

• …•Database• Workflows• Notifications

OrderService


The impact of Agile


Changes ripple through the whole architecture


Different teams. Different processes


build)

OrderManagement

(ERP)

Customer Portal


Speed is driven by the slowest


build)

OrderManagement

(ERP)

Show Products

ProductService


Most effective scenario


build)

OrderManagement

(ERP)

Show Products

ProductService


Continuous integration is a must


Automatebuild/test/staging/deploy


Performance & ScalabilityWhat happens when a web page takes 5 sec to render?


Multiple choke pointsInstrument all dependencies

9 to 5Order

Management(ERP)

Customer Portal

Product Service

Slow service?

Slow legacy

access?

Slow db access?

Infrastructurecollapse?


Architecture is driven by project needs


Front-ends “attract” functionality


Refactor Services out of the Composites


build)

OrderManagement

(ERP)

Customer Portal

ProductService

CustomerTracking

CustomerService

CustomerTracking

… and more.

Call Center


On-demand SOABottom-up instead of top-down


Agile SOA When you reach a

tipping point


Agile SOA Services/composites are categorized in

“fast” and “slow” change


Agile SOA Projects decrease in Time and Effort


Agile SOA 3 classes of teams

SOA Governance toolsProject Management


Agile SOA Managing change backlog is organized by

business line


Agile SOA Excels are sucked into central databases


Agile SOA Hidden legacy data is sucked into services


Agile SOA Real-time reporting

Analytics


Agile SOA successTechnology vs. People


• Web 2.0 • Workflow/Processes• Biz Logic • Integration• Database• WS protocols• Scheduling• Notifications

• Business centric• Stable team• Senior people• Collaborative• Communication

Technology vs. People

• Scalable

• SOA governance

• Refactoring

• Integrated life cycle

• Performance Instrumentation & Management

• Project Management


OutSystemsMarketing Pitch


Where does it fit?


agileplatform

The Agile PlatformFront-end Web 2.0 enterprise applications


agileplatform

The Agile PlatformComplete Agile SOA platform


agileplatform

agileplatform

The Agile PlatformCoexist with ESBs

Enterprise Service Bus


agileplatform

agileplatform

The Agile PlatformCoexist with BPMS

Enterprise Service Bus

BPMS


Customers135 enterprises in 16 industries (7 countries)


Over 600 apps delivered


Thank you.Get this presentation at

http://bit.ly/agile-soa

[email protected]

http://bit.ly/agile-soa

agile soa: application development in the new enterprise

Technology

agile soa

agile platformcoexist

custom build

agile

front

data

web 2

service