1. Establishing
an
SOA
Focused
Enterprise
Architecture
Asanka
Abeysinghe
WSO2,
Inc
Vice
President,
Solu5ons
Architecture

2. Goal
of
the
day
-
-
-
-
-
-
-
Service
Oriented
Architecture
Enterprise
Architecture
EA
challenges
How
SOA
helps
to
address
EA
challenges
Common
business
architecture
pa>ern
Lab
exercise
(SoluBon
building)
Q&A

3. Service
Oriented
Architecture
“Architecture
paradigm
to
build
highly
loosely
coupled
distributed
systems”

4. Service
Oriented
Architecture
cont.
“Nothing
NEW,
architecture
style
to
fix
the
broken
architectures”

5. Pre-­‐services
Era

6. SOA
at
Kindergarten

7. SOA
cont.

8. SOA
today
–
Design
Time

9. SOA
today
–
Run
Time

10. API-­‐centric
SOA
“API
Management,
the
missing
link
for
SOA
success.”
-­‐
Sanjiva
Weerawarana

11. API-­‐centric
SOA
cont.

12. API
Façade

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

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

15. The
finale
YOU’RE
FIRED!
and
MEET MY
LAWYER!

16. Building
the
Reference
Architecture
Integrati
o
n Patter
ns
Solu9on

17. L0
(Level
0)
–
Architecture

18. L1
(Level
1)
–
Architecture

19. Example
:
MDM
–
L0

20. Example
:
MDM-­‐L1

21. Business
Services
Plaaorm
:
Component
Architecture

22. BSP
:
Magnitude
View

23. BSP
:
Layered
Architecture
Integration Layer - 1
Datamodel
Integration Layer - 2
Services Platform
Business Services
Datamodel
Data Layer

24. BSP
–
ImplementaBon
:
IntegraBon
and
Data

25. BSP
–
ImplementaBon
:
Services
and
Governance

26. BSP
–
ImplementaBon
:
Business
Processes,
Security

27. BSP
–
ImplementaBon
:
Monitoring
and
Portals

28. Code
vs
ConfiguraBon
“Professional
coders
make
100-­‐150
errors
per
thousand
lines
of
code
.”

29. ConfiguraBon
Driven

30. Recap
SOA
principles
EA
challenges
Loosely
coupled
services
Loosely
coupled
development
efforts
(e.g.
accommodate
some
schedule
asynchrony)
Flexibility
under
changing
business
condiBons
Flexibility
under
changing
requirements
Fast
Bme
to
market
of
new
business
capabiliBes
Short
release
cycle
with
incremental
uBlity
Heterogeneous
environments
Choose
the
best
tool
for
each
job
Good
governance
pracBces
and
tools
Community-­‐centric
tools:
• Versioned
repository
• Peer
visibility
and
review
• Rich
communicaBon
channels
• Issue
and
status
tracking
• Automated
build/test

31. Skip
the
Ad
in
N
seconds
-­‐>|

32. Thin
slice
-­‐
Demo
- ConfiguraBon
driven
- Pa>ern
driven
- Decoupled
architecture

33. Thank
You
@asankama
hQp://asanka.abeysinghe.org
hQp://wso2.com