Roadmap to a Connected Business

403 views

Published on

Success of a Connected Business depends on robust architecture that will reuse the existing IT assets and fill the gaps by introducing required architecture layers. Having a iterative approach with a milestone plan helps to overcome the technical and non-technical challenges businesses face during implementation. Middleware and Next-Gen Middleware are the raw materials to build an integrated, secured, monitored and governed Connected Business.

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

No Downloads
Views
Total views
403
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
14
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Roadmap to a Connected Business

  1. 1. Roadmap to a Connected Business Journey for success Asanka Abeysinghe Vice President, Solutions Architecture - WSO2, Inc
  2. 2. Why Change? Increasingly Complex Requirements http://wso2.com/landing/enabling-the-connected-business
  3. 3. Challenges o Complex biz requirements o Wider problem space o Rapidly changing o Quick release cycles o ROI (from middleware) o Beyond the middleware Picture Credit : http://www.latimes.com/sports/
  4. 4. Connected Business 4 Connected Car Connected Health Connected Supply Chain
  5. 5. Connect -* 5
  6. 6. To improve is to change; to be perfect change often – Winston Churchill
  7. 7. Picture Credit : http://calebmagnino.com/creative/the-journey/ Technical Non-Technical
  8. 8. What will happen to the current system(s), data, people ?
  9. 9. When can I launch the new system ?
  10. 10. How can I get there ?
  11. 11. Next generation middleware o Big-3 o Mobile o Social o Cloud o APIs o Big Data o DevOps o Open Source Picture Credit : http://www.latimes.com/sports/
  12. 12. 13
  13. 13. Requirement Stage Requirements Current applications/systems Δ Delta
  14. 14. Approach (Architecture) Business Architecture Solution Architecture • Level 0 • Level 1 Application Architecture • Integration • Data models • APIs Runtime Architecture • Capacity Planning • Deployment • Security
  15. 15. What the Enterprise Looks Like Architecture
  16. 16. Services – get the service platforms Architecture
  17. 17. Registry/Repository Architecture
  18. 18. Identity/Access Control Architecture
  19. 19. Connectivity - internal Architecture
  20. 20. Connectivity - external Architecture
  21. 21. APIs Architecture
  22. 22. API Management the missing link of SOA success. - Sanjiva Weerawarana
  23. 23. Demand for APIs Picture Credit : http://www.newscientist.com/blogs/onepercent/2012/01/letting-gamers-experience-the.html
  24. 24. API Centric SOA BU-1 BU-2 BU-3 Services Services Services APIs API Façade
  25. 25. Monitoring, Analytics, Audits Architecture
  26. 26. Picture Credit : http://youtu.be/4Ttsx5squWg
  27. 27. CEP – real-time Architecture
  28. 28. Workflows, Rules, Pub/Sub Architecture
  29. 29. Fill-in the Blanks Architecture
  30. 30. Middleware Platform 31
  31. 31. Do I need the entire platform ?
  32. 32. Connected Business Reference Architecture
  33. 33. Beyond the middleware o Cloud o *PaaS to SaaS o Cloud native o ALM o AppFactory Private PaaS Public PaaS
  34. 34. Same programming model Same solution architecture Same (deployable) artifacts Cloud based deployment Cloud native applications
  35. 35. Connect Old-IT and New-IT Architecture
  36. 36. * Decompose your existing business processes, data and capabilities into services Make all services accessible via APIs, externally and internally Put services and APIs under control ! Build an ecosystem around your APIs Collect data on your new products and APIs http://bit.ly/1m72JSa Summary – Becoming a Connected Business
  37. 37. *

×