Upday Journey to Microservices

Slide 1

Slide 1 text

JOURNEY TO MICROSERVICES @maciejwalkowiak

Slide 2

Slide 2 text

what we’ve learnt when we applied microservices architecture

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

Greetings

Slide 7

Slide 7 text

Greetings Top News

Slide 8

Slide 8 text

Greetings Top News My News

Slide 9

Slide 9 text

STARTUP Source: https://giphy.com/gifs/season-3-money-unicorn-3osxYamKD88c6pXdfO

Slide 10

Slide 10 text

People Vector created by Freepik

Slide 11

Slide 11 text

Source: https://www.icicletech.com/blog/a-startups-guide-to-minimum-viable-product-part-1

Slide 12

Slide 12 text

Source: https://www.icicletech.com/blog/a-startups-guide-to-minimum-viable-product-part-1

Slide 13

Slide 13 text

ISSUES

Slide 14

Slide 14 text

SO .. WHAT’S THE PROBLEM? ▸ Developing new features required coordination between teams ▸ Hard to bring new feature in single sprint

Slide 15

Slide 15 text

SO .. WHAT’S THE PROBLEM? ▸ Developing new features required coordination between teams ▸ Hard to bring new feature in single sprint

Slide 16

Slide 16 text

1. horizontal teams do not work well for incremental feature development

Slide 17

Slide 17 text

CROSS FUNCTIONAL TEAMS Source: https://giphy.com/gifs/the-avengers-PpeGK6edBWAxi

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

2. Continuous delivery platform is a must

Slide 22

Slide 22 text

CURRENT ARCHITECTURE

Slide 23

Slide 23 text

CURRENT ARCHITECTURE Team X Team Y Team Z

Slide 24

Slide 24 text

CURRENT ARCHITECTURE Team X Team Y Team Z

Slide 25

Slide 25 text

ISSUES

Slide 26

Slide 26 text

SO .. WHAT’S THE PROBLEM? ▸ Adding new functionality requires changes in 2 separate services - sometimes doubles the work ▸ No clear service ownership - difﬁcult to make architecture decisions - “a camel is a horse designed by a committee" ▸ No clear bugs ownership

Slide 27

Slide 27 text

Slide 28

Slide 28 text

3. Horizontal components do not get along with vertical teams

Slide 29

Slide 29 text

API GATEWAY HTTPS://GITHUB.COM/NETFLIX/ZUUL

Slide 30

Slide 30 text

API GATEWAY

Slide 31

Slide 31 text

No content

Slide 32

Slide 32 text

API GATEWAY - MIGRATION PHASE

Slide 33

Slide 33 text

HAPPY DEVELOPERS! HAPPY MANAGERS!

Slide 34

Slide 34 text

1.000.000 users

Slide 35

Slide 35 text

4. monitoring is essential

Slide 36

Slide 36 text

No content

Slide 37

Slide 37 text

No content

Slide 38

Slide 38 text

ISSUES

Slide 39

Slide 39 text

SO .. WHAT’S THE PROBLEM? ▸ cross functional teams but many features were not crossing all technologies ▸ we ended up as two teams in a single team: android and backend ▸ teams were not oriented around business case

Slide 40

Slide 40 text

Slide 41

Slide 41 text

CROSS FUNCTIONAL TEAMS CHAOS DRIVEN DEVELOPMENT Source:https://giphy.com/gifs/four-rooms-allison-anders-alexandre-rockwell-XTYq2BBOwwSUo

Slide 42

Slide 42 text

No content

Slide 43

Slide 43 text

No content

Slide 44

Slide 44 text

ISSUES

Slide 45

Slide 45 text

SO .. WHAT’S THE PROBLEM? ▸ degrading quality ▸ no feeling of responsibility for production issues ▸ increasing overall system complexity

Slide 46

Slide 46 text

SO .. WHAT’S THE PROBLEM? ▸ degrading quality ▸ no feeling of responsibility for production issues ▸ increasing overall system complexity

Slide 47

Slide 47 text

5. stable,,teams and ownership matter

Slide 48

Slide 48 text

6. TeAms built around features are fast

Slide 49

Slide 49 text

TEAMS BUILT AROUND BUSINESS CAPABILITIES Source: https://giphy.com/gifs/ﬁre-ofﬁce-yolo-OongkSFTbly8w

Slide 50

Slide 50 text

Slide 51

Slide 51 text

No content

Slide 52

Slide 52 text

7. modular architecture matters

Slide 53

Slide 53 text

8. there is always a monolith. embrace it

Slide 54

Slide 54 text

T-SHAPE DEVS

Slide 55

Slide 55 text

ok but what about architecture?

Slide 56

Slide 56 text

ARCHITECTURE PRINCIPLES ▸ no ivory tower architect ▸ as little upfront architecture as possible ▸ subsystems communicate with each other over RabbitMQ ▸ databases are not shared between services ▸ avoid cascading synchronous communication in user ﬂow ▸ keep it simple on every level

Slide 57

Slide 57 text

1. horizontal teams do not work well for incremental feature development 2. Continuous delivery platform is a must 3. Horizontal components do not get along with vertical teams 4. monitoring is essential 5. stable teams and ownership matter 6/. teams built around features are fast 6. modular architecture matters 7. there is always a monolith. embrace it