Patterns provide structure and clarity, enabling architects to establish their solutions across the enterprise. Moreover, these software patterns also help to link technology and business requirements in an effective and efficient manner. Patterns help to incorporate robust solutions for business problems due to it’s wide adoption as well as it’s reusability. In addition, patterns create a common method to communicate, document and describe solutions. This session will explain some of these patterns ranging from SOA (Service-Oriented Architecture), WOA (Web-Oriented Architecture), EDA (Event Driven Architecture), and IoT (Internet of Things)

1. Pattern-Driven Enterprise
Architecture
Asanka Abeysinghe
Vice President, Solutions Architecture - WSO2,Inc
QCon Sao Paulo - 2015

2. 2
10:50- 11:40 11:55-12:45 14:15-15:05
PATTERN DRIVEN
ARCHITECTURE
SECURING THE
INSECURE
CREATING AN API
CENTRIC ENTERPRISE
15:35-16:25 16:40-17:30
NEXT-GEN APPS WITH IOT
AND CLOUD
PANEL: BUILDING
TOMORROW’SENTERPRISE: REPORTS
FORM THE GROUND WARS

3. Patterns
3
A generic solution for a common recurring
problem.
 Used it before
 Error proof
 Common way to communicate : architect’s language
 Catalog to pick one : feel comfortable

4. Enterprise Architecture
4
“Manage the complexity of the IT
environment and applies principles and
techniques to reduce the complexity,
improve efficiencies, and reduce
capital and operational expenditure.”

5. 5

6. Service Oriented Architecture (SOA)
6
“Architecture paradigm to build
highly loosely coupled distributed
systems”

7. SOA cont….
7
“Nothing NEW, architecture style to fix
the broken architectures”

8. SOA at kindergarten
8

9. SOA improved
9

10. SOA improved
10

11. SOA runtime view
11

12. 12
 Less visibility to projects
o Difficult to find
o Availability
o Ownership
 Development cycles:
o From 18 to 6 months to 3 months
 Change management
 Real standards
o Technical (REST, SOAP, protobuf)
o Business (ACORD, HL7, FIX, FAST)
 Integration is key (extend to connected
business)
o Companies without integration are falling
behind
o Heterogeneous systems
Enterprise Architecture has changed

13. 13
Next-Gen Middleware
 Big-3
o Mobile
o Social
o Cloud
 APIs
 Big Data
 DevOps
 Open Source Picture Credit : http://www.latimes.com/sports/

14. Enterprise App Store
API Management SaaS Adoption
Executive Dashboards
PaaS
Mobile Apps
Open Source Adoption
SOA
Cloud Adoption and Automation
Federated Identity
Social Networking
Mobile BYOD
Big Data and Analytics

15. Modern Applications are
Systems of Systems

16. Gartner View of Systems of Systems

17. Forrester View of Systems of Systems
Systems of record are technologies
that manage and store transactions,
content, and processes.
Systems of engagement are
technologies that directly support
customer interactions through
software.
Systems of automation are
technologies that intelligently manage
physical products, networks, and
infrastructure.
Source: Forrester Research

18. Systems of Systems Functional Requirements

19. Supportive patterns
19
 Event-Driven Architecture (EDA)
 Web Oriented Architecture (WOA)
 Enterprise Integration Patterns
 Internet of Things (IoT)

20. How can I get there ?

21. Requirement stage
21
Requirements
Current
applications/systems
Δ Delta

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

23. Level 0 architecture
23

24. Level 1 architecture
24

25. Example : MDM L0
25

26. Example : MDM L1
26

27. What the Enterprise Looks Like
Architecture

28. Identity/Access Control
Architecture

29. Services – get the service platforms
Architecture

30. Registry/Repository
Architecture

31. Connectivity - internal
Architecture

32. Connectivity - external
Architecture

33. APIs
Architecture

34. Monitoring, Analytics, Audits
Architecture

35. CEP – real-time
Architecture

36. Fill-in the Blanks
Architecture

37. Middleware Platform
37

38. Do I need the entire platform ?

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

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

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

42. Connect Old-IT and New-IT
Architecture

43. People
43
 Engage
 Empower
 Accountable
 Iterative

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

45. 45

46. 46
Obrigado ….!
Connect : @asankama | asankaa AT wso2.com | http://asanka.abeysinghe .org