Most organizations engaged in transformation today are moving from left to right in digitally-driven maturity models. The objectives are well known: increase agility, boost productivity, and provide seamless digital experiences for consumers. Architects play a pivotal role as the curators of this transformation. In this session, Asanka will share his experience on how architects can contribute and introduce a framework to follow on refactoring enterprises.

1. Asanka Abeysinghe | Chief Technology Evangelist | WSO2, Inc | @asankama
Architecting the Transformation
Convert architecture into a value stream generator
February, 18 2021 #architect2architect https://wso2.com/

2. 2019
1997 2003
Architect
2012
VP Solutions
Architecture
2001 2008
Director
Solutions
Architecture
Deputy CTO
Open Source
Distributed Computing
Programmer
COBOL
OLE, OLE2
COM, COM+
DCOM
CORBA
Java Developer
J2EE
MMS
286-DX4
Eventing
FIX
HL7
CONNECT-health
Global architecture team
500+ customers
Champions program
Chief Architect
2005
QSP
AR
Trusted advocate
Game hacker
C++ programmer
Age-16
Hedge fund tools
Ref. Architecture
Ref. Methodology
Evangelize
2018
Middleware Developer/Architect
Entrepreneur
Chief Technology
Evangelist
2020
Connecting humans & technology
Architecting the transformation
2

3. Next 45-minutes
Journey of an architect
Intro
Transformation
Architect
Architecture
Delta
Strategy to execution
Contribution
3

4. Transformation
4
Intro
Transformation
Architect
Architecture
Delta
Strategy to execution
Contribution

5. Everyone in a transformation.
5

6. 7 YEARS
In a few months
Leapfrogged by
Source: https://www.consultancy.uk/news/26372/covid-19-has-accelerated-digital-transformation-by-seven-years
6

7. • Crowded market
• Multiple options
• Best experience
• Competitive advantage
Business models
Di
ff
erentiators
Industry speci
fi
c
Common capabilities
7

8. Digitally-driven organization
• Decentralized
• Lean agile
• Open-*
• Customer-centric
• Cloud-native technologies
• Data-driven
Design principles
8 Image credit: https://www.
fl
ickr.com/photos/visualpunch/

9. Transformation objectives
9

10. Maturity model
10

11. 11

12. “Iteratively move to the right”
12

13. Role of the architect
13
Intro
Transformation
Architect
Architecture
Delta
Strategy to execution
Contribution

14. Wicklow, Ireland
Spring-2004
14
Product strategy White boarding Coding
Eric Nadalin Denis Hennessy
- Credibility
- Impact to the system
- Storyteller
- Visual
- Not Powerpoint architecture

15. Architect is a warrior -
who protects the
organization by finding
solutions and link
business and technology.
15

16. Architect has a guide.
16

17. Architect is a curator.
17

18. Architecture
18
Intro
Transformation
Architect
Architecture
Delta
Strategy to execution
Contribution

19. A specification?
19

20. A diagram?
20

21. A value stream generator.
21

22. 22

23. 23
Source: https://dzone.com/articles/future-retail-a-business-and-technical-architectur
Business
Architecture

24. Information Architecture
24
Consumption focused
Agregates
Historical data
Relationship data
(Normalized/documented)
Raw data
$
Idea Credit: Jennifer Lim - Data Technology Strategic Exec.

25. Application Architecture
25

26. Technology Architecture
26

27. Delta
27
Intro
Transformation
Architect
Architecture
Delta
Strategy to execution
Contribution

28. Gap
Strategy into execution - messy middle
Layered and centralized
Shadow IT
Siloed: brown
fi
eld and green
fi
eld
Disconnected: architect | developer | devops
AgileWaterfall, Wagile
28

29. Execution
29
Intro
Transformation
Architect
Architecture
Delta
Strategy to execution
Contribution

30. 30
Principles
drive
decisions

31. Values define using the business architecture
31
Business Strategy
Business Outcome
Business Outcome Business Outcome
Concept Consumption
Value stream
Value Value Value
Initiatives

32. Distributed information architecture
32

33. Modernize data architecture
33
Source:https://medium.com/architect2architect/microdata-architecture-5449596a3f6f

34. Simplified
34
Delivery
channel
API Services
Quality of services
Integration
System
of
record
Level 0 Level 1

35. Decentralized
35

36. Separation of concerns
36

37. Operational model
37

38. Execution model
38

39. More in the architect’s battle card
Domain-driven (domain == cell)
Programmability
Composable with APIs
Inside out approach
Projects to products
Design on the cloud for the cloud
39

40. Contribution
40
Intro
Transformation
Architect
Architecture
Delta
Strategy to execution
Contribution

41. Authored
• Cell-based Architecture: https://github.com/wso2/reference-architecture/blob/master/reference-architecture-cell-based.md
• Layered and Segmented: https://github.com/wso2/reference-architecture/blob/master/reference-architecture-layered-segmented.md
• Agile Methodology: https://github.com/wso2/reference-methodology/blob/master/reference-methodology.md
• Cellular Enterprise: https://www.forbes.com/sites/forbestechcouncil/2020/06/29/the-cellular-enterprise
• Architect to architect: https://medium.com/architect2architect
41

42. #architect2architect
42
https://wso2.com/