Gartner Application Architecture Summit 2011 Notes for a Banking Software Company Paul Fryer, Fiserv
CLOUD
Why Cloud? <ul><li>Quick answer: Money! </li></ul><ul><li>Elastic  – can scale up and down in real time.  </li></ul><ul><l...
How can we leverage public cloud? <ul><li>Can go in cloud </li></ul><ul><li>Images (campaign manager) </li></ul><ul><li>UI...
 
MOBILE
What should be mobilized?  <ul><li>Retail and Small Business. </li></ul><ul><li>Need to start thinking in terms of Mobile ...
How to mobilize <ul><li>Work with Fiserv’s mobile group. </li></ul><ul><li>Evaluate vender solutions. </li></ul><ul><ul><l...
SOCIAL
Why Social? Pave the cow paths…  Almost 10% of the world is on facebook.
How can we leverage social technologies? <ul><li>Traditional Support Messaging </li></ul><ul><li>Forces customer to use sp...
IN MEMORY
Why In Memory? <ul><li>The cost of memory has drastically decreased, creating opportunities for performance and scale. </l...
How can we leverage Memory DBs? <ul><li>Use for session context. </li></ul><ul><li>High IO databases/tables are candidates...
NEXT STEPS
Do This
Upcoming SlideShare
Loading in …5
×

Gartner application architecture summit 2011

1,272 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,272
On SlideShare
0
From Embeds
0
Number of Embeds
556
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Gartner application architecture summit 2011

  1. 1. Gartner Application Architecture Summit 2011 Notes for a Banking Software Company Paul Fryer, Fiserv
  2. 2. CLOUD
  3. 3. Why Cloud? <ul><li>Quick answer: Money! </li></ul><ul><li>Elastic – can scale up and down in real time. </li></ul><ul><li>Quicker Time to Market – Less time to procure infrastructure, coordinate resources, and deploy code. </li></ul><ul><li>These aspects can lower development and deployment costs while providing a more agile application delivery platform. </li></ul>
  4. 4. How can we leverage public cloud? <ul><li>Can go in cloud </li></ul><ul><li>Images (campaign manager) </li></ul><ul><li>UI resources (COL) </li></ul><ul><li>UI presentation tier (possibly) </li></ul><ul><ul><li>Might require re-architecture of UI to be more “cloud friendly” </li></ul></ul><ul><ul><ul><li>No hard drive access. </li></ul></ul></ul><ul><ul><ul><li>Really need to make everything SOA. </li></ul></ul></ul><ul><li>Can’t go in cloud </li></ul><ul><li>Bank account numbers </li></ul><ul><li>Social security numbers </li></ul><ul><li>User credentials </li></ul><ul><li>Anything secure or private </li></ul><ul><li>Keep service layer in private cloud. </li></ul><ul><ul><li>The service layer needs to connect to protected systems, so it won’t go in cloud. </li></ul></ul>
  5. 6. MOBILE
  6. 7. What should be mobilized? <ul><li>Retail and Small Business. </li></ul><ul><li>Need to start thinking in terms of Mobile First. </li></ul><ul><ul><li>New POCs should be mobile. </li></ul></ul><ul><ul><li>How will development address more than just the desktop channel? </li></ul></ul>
  7. 8. How to mobilize <ul><li>Work with Fiserv’s mobile group. </li></ul><ul><li>Evaluate vender solutions. </li></ul><ul><ul><li>Cross compilers (write once, run anywhere) </li></ul></ul><ul><li>Use device detection to build dynamic web applications that server multiple channels. </li></ul>
  8. 9. SOCIAL
  9. 10. Why Social? Pave the cow paths… Almost 10% of the world is on facebook.
  10. 11. How can we leverage social technologies? <ul><li>Traditional Support Messaging </li></ul><ul><li>Forces customer to use specific channel (OLB). </li></ul><ul><li>Slow </li></ul><ul><li>Desktop </li></ul><ul><li>Closed </li></ul><ul><li>Cost center </li></ul><ul><li>Social Support Messaging </li></ul><ul><li>Allows customer to use their preferred channel (twitter, facebook, etc.) </li></ul><ul><li>Fast, real time messaging. </li></ul><ul><li>Mobile </li></ul><ul><li>Open – in certain contexts. </li></ul><ul><li>Marketing opportunities (through the network) </li></ul>
  11. 12. IN MEMORY
  12. 13. Why In Memory? <ul><li>The cost of memory has drastically decreased, creating opportunities for performance and scale. </li></ul><ul><li>Low latency. </li></ul><ul><li>Memory databases have now crossed the 1 terabyte size. You can literally run entire databases in memory. </li></ul>
  13. 14. How can we leverage Memory DBs? <ul><li>Use for session context. </li></ul><ul><li>High IO databases/tables are candidates for moving to in memory databases. </li></ul><ul><ul><li>Account Lists </li></ul></ul><ul><ul><li>Transaction History </li></ul></ul><ul><ul><li>Payees </li></ul></ul>
  14. 15. NEXT STEPS
  15. 16. Do This

×