-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
177 lines (105 loc) · 2.58 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
<!DOCTYPE html>
<html>
<head>
<title>Hexagonal Architecture</title>
<meta charset="utf-8">
<style>
body { font-family: 'Arial'; }
h1, h2, h3 {
font-family: 'Arial';
font-weight: normal;
}
.remark-code, .remark-inline-code { font-family: 'Ubuntu Mono'; }
</style>
</head>
<body>
<textarea id="source">
class: center, top
# Hexagonal Architecture
---
class: center, top
### Hexagonal Architecture / Ports and Adapters
#### Hexagonal Architecture is an architectural style that moves programmer’s focus from conceptual layers to a distinction between the software’s inside and outside parts.
---
class: center, top
### Multi-Tier Architecture
---
class: left, top
### .center[Drawbacks of the Multi-Tier Architecture]
.center[]
* Where is the application core?
* Businesslogic can be find in every layer
* It can be hard to implement tests
---
class: left, top
### .center[Hexagonal Architecture]
##### The outside part:
* UI
* database
* messaging
* ...
##### The inside part:
* core domain
---
class: center, top
### Ports and Adapters
---
class: left, top
### .center[Motivation]
* Building the application around the core (domain)
* Create fully testable systems
---
class: center, top
### Multi-Tier Architecture
---
class: center, top
### Multi-Tier Architecture
---
class: center, top
### Ports and Adapters
---
class: center, top
### Ports and Adapters
---
class: left, top
### .center[Ports and Adapters]
* Ports: What
* Adapters: How
---
class: left, top
### .center[Principles]
* The inside part knows nothing about the outside part
* You should be able to use any adapter that fits a given port
* No use case or domain logic goes to the outside part
---
class: center, middle
## But why is it called hexagonal?
---
class: center, middle
---
class: center, middle
to avoid one-dimensional thinking about the architecture
---
### Links
* https://dzone.com/articles/hexagonal-architecture-is-powerful
* http://java-design-patterns.com/blog/build-maintainable-systems-with-hexagonal-architecture/
---
class: center, middle
</textarea>
<script src="remark-latest.min.js">
</script>
<script>
var slideshow = remark.create();
</script>
</body>
</html>