An evolutionary architecture supports incremental, guided change across multiple dimensions. For many years, software architecture was described as the “parts that are hard to change later”. But then microservices showed that if architects build evolvability into the architecture, change becomes easier. This talk, investigates the family of software architectures that support evolutionary change, along with how to build evolvable systems.

1. 1
Andy Marks

2. 2

3. 3
evolutionary architecture
definition

4. 4
evolutionary architecture

5. change
20132006 2007 20152000

6. for the record...

7. 7
guided
fi s n i n

8. 8
incremental change
re e

9. 9

10. 10

12. 12
tl;dr

13. fitness function
definition

14. y = f(x)
so da
as s t

15. y = f(x)
●
●
●
●
●
●
●
●
●
characteristics

16. y = f(x)●
●
●
●
●
●
sources●
●
●
●
●
●
●
●
●

17. prior art @ nab
S3 C A
C C y e m
Ser En i s

18. still interested?

19. 19

21. 21
tl;dr

22. styles

23. criteria

24. Incremental
change
Fitness
functions
Appropriate
coupling
Monolithic
- Unstructured
- Layered
- Microkernel
- Modular
:-(
:-|
:-)
:-)
:-|
:-)
:-)
:-|
:-(
:-)
:-)
:-)
Service oriented
- ESB-based
- Microservices
- Service-based
:-(
:-)
:-)
:-(
:-)
:-|
:-(
:-|
:-|
Event driven
- Brokers
- Mediators
:-)
:-)
:-)
:-)
:-)
:-(
Serverless :-) :-| :-|
Big Ball of Mud :-( :-( :-(

25. ●
M
onolithic
●
ESB-based
SO
A
●
M
icroservices
●
Broker-based
EDA
...

26. ● "total unification of the domain
model for a large system will not be
feasible or cost-effective"
● Divide a large system into smaller
Bounded Contexts (BC)
● “a conceptual boundary where a
domain model is applicable.”
bounded context

27. 27

30. inappropriate
governance

32. code reuse
abuse

34. premise

36. 36

37. parting thoughts

38. parting thoughts

39. parting thoughts

40. parting thoughts

41. parting thoughts

42. 42

43. Your contact at ThoughtWorks
Wayne Te Paa
Email:
Phone: