Gartner Application Architecture Summit 2011

Notes for a Banking Software Company

Paul Fryer, Fiserv

CLOUD

Why Cloud?

• Quick answer: Money!• Elastic – can scale up and down in real time. • Quicker Time to Market – Less time to procure

infrastructure, coordinate resources, and deploy code.

• These aspects can lower development and deployment costs while providing a more agile application delivery platform.

How can we leverage public cloud?

Can go in cloud• Images (campaign manager)• UI resources (COL)• UI presentation tier

(possibly)– Might require re-architecture

of UI to be more “cloud friendly”• No hard drive access. • Really need to make

everything SOA.

Can’t go in cloud• Bank account numbers• Social security numbers• User credentials• Anything secure or private• Keep service layer in private

cloud.– The service layer needs to

connect to protected systems, so it won’t go in cloud.

MOBILE

What should be mobilized?

• Retail and Small Business.• Need to start thinking in terms of Mobile First.– New POCs should be mobile.– How will development address more than just the

desktop channel?

How to mobilize

• Work with Fiserv’s mobile group.• Evaluate vender solutions.– Cross compilers (write once, run anywhere)

• Use device detection to build dynamic web applications that server multiple channels.

SOCIAL

Why Social?

Pave the cow paths… Almost 10% of the world is on facebook.

How can we leverage social technologies?

Traditional Support Messaging

• Forces customer to use specific channel (OLB).

• Slow• Desktop• Closed• Cost center

Social Support Messaging• Allows customer to use

their preferred channel (twitter, facebook, etc.)

• Fast, real time messaging.• Mobile• Open – in certain contexts.• Marketing opportunities

(through the network)

IN MEMORY

Why In Memory?

• The cost of memory has drastically decreased, creating opportunities for performance and scale.

• Low latency.• Memory databases have now crossed the 1

terabyte size. You can literally run entire databases in memory.

How can we leverage Memory DBs?

• Use for session context.• High IO databases/tables are candidates for

moving to in memory databases.– Account Lists– Transaction History– Payees

NEXT STEPS

Do This