This document provides a roadmap for connecting a business through modernizing the middleware and APIs. It discusses challenges like complex requirements and rapid release cycles. The roadmap includes assessing current systems, defining the business and solution architecture, and developing APIs and services. It also covers runtime concerns like deployment, security, and monitoring. The goal is to break processes into reusable services, expose services through APIs, manage the API ecosystem, and collect data to continuously improve.

1. Roadmap to Connected Business
Complete your corporate jigsaw
Asanka Abeysinghe
Vice President, Solutions Architecture
WSO2, Inc

2. Expectation
Experience
Experience - attentive listeners

6. Everything should be
made as simple as
possible, but not
simpler. - Albert Einstein

7. Do I need the entire
platform ?

8. What will happen to the
current system(s), data,
people ?

9. When can I launch the
new system ?

10. When can I launch the
new system ?

11. How can I get there ?

12. Challenges
• Complex biz requirements
– Wider problem space
– Rapidly changing
• Quick release cycles
• ROI (from middleware)
• Beyond the middleware
Picture Credit : http://www.latimes.com/sports/

14. Next generation middleware
• Big-3
– Mobile
– Social
– Cloud
• APIs
• Bigdata
• DevOps
• Open Source Picture Credit : http://www.latimes.com/sports/

16. Technical Non-Technical
Picture Credit : http://calebmagnino.com/creative/the-journey/

17. Requirement stage
Requirements
Current
applications/systems
Δ Delta

18. Business
Architecture
Solution
Architecture
• Level 0
• Level 1
Application
Architecture
• Integration
• Datamodels
• APIs
Runtime
Architecture
• Capacity Planning
• Deployment
• Security
Approach (Architecture)

19. What the enterprise look like Architecture

20. Services – get the service platforms Architecture

21. Story : New datamodel in a
week

22. Registry/Repository Architecture

23. Identity/Access control Architecture

24. Story : Security bridging

25. Connectivity - internal Architecture

26. Connectivity - external Architecture

27. Story : Added latency

28. APIs Architecture

29. API Management the
missing link of SOA
success. - Sanjiva Weerawarana

30. API Centric SOA
APIs
API Façade
Services Services Services
BU-1 BU-2 BU-3

31. Demand for APIs
Picture Credit : http://www.newscientist.com/blogs/onepercent/2012/01/letting-gamers-experience-the.html

32. Demand for APIs – cont..

33. Monitoring, analytics, audits Architecture

34. Picture Credit : http://youtu.be/4Ttsx5squWg

35. CEP – real-time Architecture

36. Workflows, rules, pub/sub Architecture

37. Fill in the blanks Architecture

38. Beyond the middleware
• Cloud
– *PaaS to SaaS
– Cloud native
• ALM
– AppFactory
Private
PaaS
Public
PaaS

39. Same programming model
Same solution architecture
Same (deployable) artifacts
Cloud based deployment
Cloud native applications

40. Connect Old-IT and New-IT Architecture

41. Becoming a Connected Business – 5 steps
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

42. To improve is to change;
to be perfect change
often – Winston Churchill

43. Story : Change – not CMC

45. Picture Credit : http://calebmagnino.com/creative/the-journey/

46. Thank You