Let's dive into the exciting world of architecture! As a solution architect, you'll use your tech-savvy skills to solve complex business problems. But it's not just about the tech - you'll need to understand the business goals, work with stakeholders, and make tough trade-offs. In this walk, we'll take a sample project and go through the stages of architectural design. You'll learn how to gather requirements, create a system design, and communicate your decisions effectively. By the end, you'll be equipped with the practical knowledge to become a successful architect. So, are you ready to unleash your inner architect and build something amazing? Let's go!

1. Unlocking the secrets of successful architects
what skills and traits do you need?
Constantine Slisenka
Java Tech Lead @ Playtika

2. 2

3. 3
uncertainty

4. 4
structure

5. The architect’s framework
5
1. Business goals
2. Architecture significant requirements (ASR)
3. Stakeholders
4. Non-functional requirements
5. Constraints
6. Trade-offs
7. Communication

6. 6

7. “About the
important stuff,
architecture is.
Whatever that is”
7

8. Architecture significant
requirements (ASR)
8

9. 9
ASR
(Architecture Significant Requirement)
The architecture might well be dramatically different
in the absence of such a requirement

10. Business goals
10

11. 11
Sell game
resources for
republic
credits
Engage users in the
game, more options to
earn and spend
resources
Special
missions!

12. 12

13. 13

14. Stakeholders
14

15. “The path to the dark side,
poor understanding of
stakeholders is.
Wrong design decisions it
leads to.
Wrong software it leads to.
Business failure it leads to.”
15

16. 16
Your most important skill an architect is …
empathy
be interested in others, learn about their needs, take the
time to listen and try to understand their perspective

17. 17
1. Product managers and game designers
2. Monetisation
3. Economy
4. Operations
5. Customer support
6. Artists
Stakeholders in Playtika

18. 18

19. 19

20. Non-functional
requirements
20
● Performance
● Data consistency
● Availability
● Observability
● Scalability
● Security
● …

21. 21

22. Constraints
Trade-offs
22

23. 23
Architecture
Constraints

24. 24
● Time
● Budget
● Development team
● Approved technology stack
● Company policies
● …

25. Trade-offs
25
● Sync vs async
communication
● Eventual vs strong
consistency
● Low latency vs
computing in the
background
● Use existing component
vs build new
● …

26. 26

27. Communication
27

28. “Pass on
what you have
learned”
28

29. 29

30. Working with
changing requirements
30

31. “Always in
motion is
the future...”
31

32. 32

33. Books
33

34. 34

35. Questions?
Constantine Slisenka
Java Tech Lead @ Playtika