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.

1. Roadmap to a Connected
Business
Journey for success
Asanka Abeysinghe
Vice President, Solutions Architecture - WSO2, Inc

2. Why Change? Increasingly Complex Requirements
http://wso2.com/landing/enabling-the-connected-business

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. Connected Business
4
Connected Car
Connected Health
Connected Supply Chain

5. Connect -*
5

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

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

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

9. When can I launch the
new system ?

10. How can I get there ?

12. 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/

13. 13

14. Requirement Stage
Requirements
Current
applications/systems
Δ Delta

15. Approach (Architecture)
Business
Architecture
Solution
Architecture
• Level 0
• Level 1
Application
Architecture
• Integration
• Data models
• APIs
Runtime
Architecture
• Capacity Planning
• Deployment
• Security

16. What the Enterprise Looks Like
Architecture

17. Services – get the service platforms
Architecture

18. Registry/Repository
Architecture

19. Identity/Access Control
Architecture

20. Connectivity - internal
Architecture

21. Connectivity - external
Architecture

22. APIs
Architecture

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

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

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

26. Monitoring, Analytics, Audits
Architecture

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

28. CEP – real-time
Architecture

29. Workflows, Rules, Pub/Sub
Architecture

30. Fill-in the Blanks
Architecture

31. Middleware Platform
31

32. Do I need the entire
platform ?

33. Connected Business Reference Architecture

34. Beyond the middleware
o Cloud
o *PaaS to SaaS
o Cloud native
o ALM
o AppFactory
Private
PaaS
Public
PaaS

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

36. Connect Old-IT and New-IT
Architecture

37. *
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

38. *