modernizing your aging architecture: what enterprise architects need to know about going reactive

29

Upload: typesafeinc

Post on 06-Aug-2015

5.832 views

Category:

Software


1 download

TRANSCRIPT

Page 1: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive
Page 2: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

Modernizing Your Aging ArchitectureMichael Facemire, Principal Analyst

June 24, 2015

Page 3: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 3

Opportunity & Challenges

Page 4: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 4

Enterprise Mobility Challenges

Backend

Integration/Federation

Channel

Security

Client-side

Development

Delivery & Organization Challenges

MAM

MD

M

API ?

?

?Fast!

Page 5: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 5

Software — approaching a zero-day event!D

eliv

ery

time

Yest

erda

y

Tom

orro

w

Zero-day

2-4 months

12-18 months

Page 6: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

Heritage Architecture

Page 7: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

Modular Architecture

Page 8: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 8

AP

I Layer

Delivery Layer

Where is the experience created?

Page 9: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 9

Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

V 1.0 (MVP)

V 1.2.2V 1.2V 1.2.1

Regression + Emergency Patch

New OS version released

V 2.0V 2.1

Features +Defect fixes

Regular Internal Sprint Cycle + Beta Testing (2 weeks)

A Typical Mobile App Release Schedule

Page 10: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 10

Are You Experienced?

User Experience

Performance

Page 11: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 11

The Enterprise Backend Challenge

SOAP XML-RPC REST SQL MQ

Systems

Of

Record

RESTJSON OAUTH

Mobile Devices, Internet of Things, M2M

LOB Apps Directory CMS CRM

??

?

??

?

Page 12: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 12

Architecture Discussion

Page 13: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 13

Let’s Learn From Our Mistakes

Business

Application

Business

Application

Business

Application

Static

HTML!! Servlets!! XML +

XSLT!!

Page 14: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 14

Mobile Integration Value

Business

Application

Business

Application

Business

Application

RESTful API Layer

Mobile SDK/Libraries

Page 15: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 15

Current Web Implementations Are Broken

Today’s Web Reality Mobile’s Requirements

Agility The application layer is hard-coded to the data and presentation layers

Dynamically composed services that support contextual experiences

Scalability Services cannot rise and fall with changing demand

Distributed deployment for performance and rapid scaling

Flexibility Monolithic solutions, not a composition of best-of-breed offerings

Loosely coupled components to support wireless clients aggregated services

Page 16: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 16

Four-tier Architecture

Services

Aggregation

Delivery

Client

3rd Party Apps

DB CRM ERP

Web Services/ESBExternalServices

Content Cache & Optimization

Content Transformation

Mobile GlassWearables

Service Aggregation/Federation

Identity Federation

Security Endpoint

Protocol Transformation

M2M

Business PartnerServicesMaintain Velocity & Modularity

Elastic & Rapid Development

Granular & Rapid Content Delivery

Every Front-end Channel

Page 17: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 17

Ser

vice

s

CRMLOB Apps CMS Directory

Service API

Aggregation Tier In Detail

Service API

Service API

Service API

Service API

Service API

Aggregation Tier A

ggre

gatio

n T

ierFederated Access Layer

Business Process API

Business Process API

Business Process APIBusiness

Process API

Delivery TierClient Tier

App 1 App 2

Eng

agem

ent

Con

text

Ser

vice

sBusiness

Intelligence

Analytics

Role-based

Access

Page 18: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 18

Paradigm Transformation

Model

View

Controller Model

View

ControllerTightly Coupled

Disconnected,

Asynchronous

YESTERDAY TOMORROW

Page 19: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

Multiple Canonical Models

Page 20: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

Asynchronous Boundaries

Page 21: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 21

Moving From This…

UI Presentation LayerHTML/JavaScript/CSS

UI Generation LayerJava/.Net

Business LogicJava/.Net

Page 22: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 22

To This!

UI Presentation LayerHTML/JavaScript/CSS

UI Generation Layer

Business LogicJava/Scala/.Net

Page 23: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 23

Performance And Scale Matter

Page 24: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 24

Composition is the Future

V C

M

Page 25: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

© 2015 Forrester Research, Inc. Reproduction Prohibited 25

Start at the bottom

Services

Aggregation

DB CRM ERP

Web Services/ESBExternalServices

Service Aggregation/Federation

Identity Federation

Security Endpoint

Protocol Transformation

Business PartnerServices

• Create all new services with a consumable API.• Investigate API solutions for existing services.• Hint: Application modernization budgets can help!

Page 26: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

26

Online Services

IoT

Retail

Education

Technology

Social

Media

Finance

Who has succeeded in architecture modernization?Source: Typesafe

Page 27: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

Modernize with Proven TechnologySource: Typesafe

27

Conversions up 20%Mobile orders up 98%

Achieved > 10x performance improvement…on the same hardware

Reduced code base by 99% from 479,000 to 5,000 lines

Improved elasticity to handle 100X increase in traffic

Modernized from monolithto microservices

Radically simplified toolset and architecture freed developers to

deliver rapid innovation

Page 28: Modernizing Your Aging Architecture: What Enterprise Architects Need To Know About Going Reactive

How they did it:Typesafe Project Success Subscription (PSS)

• Full Lifecycle Support• Access to our engineering team; Best practices

• Support Service Level Agreements (SLAs)• Up to 1 hour 24/7 SLA

• Certified Build• Validated integrations; Backwards compatible patches

• Training and Consulting• Commercial Licensing Options• Ongoing Knowledge Transfer• Developer Recruitment and Speaking Opportunities