nothing like Jon Snow.

1. Software Architecture in Microservices
Passapong Thaithatgoon.

2. Architecture is about the :
“overlaps of dimensions”

3. Architecture is about the :
“overlaps of dimensions”
which each dimension handle each constraints
constraint
constraint
constraint
constraint
constraint

4. Architecture is about the :
“overlaps of dimensions”
which each dimension handle each constraints
constraint
constraint
constraint
constraint
constraint
so the dimension layer out the problems context

5. And Overlaps…
would be growth in greater context.

6. it start from “Piece by Piece”

7. Combine as Module
each module handle each constraint

8. so each module
“Solve That Constraint”

9. so each module
“Solve That Constraint”
and also..
“Bring Those Constraints”

10. Naming
is the smallest “Building Block” of Software Architecture
of variable or function

11. which you
“can do it Big or Small.”
Small one
Big one

12. Small one
fun isVowel(character: Char) {
val vowels = {A, E, I , O, U}
vowels.contains(character.toUpperCase)
}
fun countVowel(word: String) {
word
.foreach(char => isVowel(char))
.count
}

13. Big one
fun countVowel(word: String) {
val vowels = {A, E, I , O, U}
word
.foreach(char =>
vowels.contains(char.toUpperCase))
.count
}

14. Small one
fun isVowel(character: Char) {
val vowels = {A, E, I , O, U}
vowels.contains(character.toUpperCase)
}
fun countVowel(word: String) {
word
.foreach(char => isVowel(char))
.count
}
fun filterVowel(word: String) {
word
.filter(char => isVowel(char))
}
Small one
Small can bring reusability

15. Big one
fun countVowel(word: String) {
val vowels = {A, E, I , O, U}
word
.foreach(char =>
vowels.contains(char.toUpperCase))
.count
}
Big can get the job done faster

16. Small or Big
which is suitable ???
Maintainability Agility

17. As you Know Architecture
“Work with Constraints”

18. so
“Time is Constraint”

19. “Space also a Constraint”

20. Small or Big
each solution brings each constraint
Maintainability Agility
Space Time