Tweet
Tweet

Slide 1

Slide 1 text

@MarcDuiker

Slide 2

Slide 2 text

@MarcDuiker Marc Duiker Sr Developer Advocate

Slide 3

Slide 3 text

@MarcDuiker 3

Slide 4

Slide 4 text

@MarcDuiker 4

Slide 5

Slide 5 text

@MarcDuiker 5

Slide 6

Slide 6 text

@MarcDuiker 6

Slide 7

Slide 7 text

@MarcDuiker 7

Slide 8

Slide 8 text

@MarcDuiker 8

Slide 9

Slide 9 text

@MarcDuiker 9 https://en.wikipedia.org/wiki/Monolithic_application “In software engineering, a monolithic application describes a software application that is designed without modularity.”

Slide 10

Slide 10 text

@MarcDuiker 10 https://en.wikipedia.org/wiki/Modularity “…modularity is the degree to which a system's components may be separated and recombined, often with the benefit of flexibility and variety in use.”

Slide 11

Slide 11 text

@MarcDuiker App Server DB Server

Slide 12

Slide 12 text

@MarcDuiker 13 Function App Function App Queue Storage

Slide 13

Slide 13 text

@MarcDuiker 14 Function App Function App Queue Database

Slide 14

Slide 14 text

@MarcDuiker 15

Slide 15

Slide 15 text

@MarcDuiker 16

Slide 16

Slide 16 text

@MarcDuiker 17

Slide 17

Slide 17 text

@MarcDuiker 18

Slide 18

Slide 18 text

@MarcDuiker 19 https://martinfowler.com/articles/agileStory.html “We eventually agreed on "agile" as we felt that captured the adaptiveness and response to change which we felt was so important to our approach…”

Slide 19

Slide 19 text

@MarcDuiker 20

Slide 20

Slide 20 text

@MarcDuiker 21

Slide 21

Slide 21 text

@MarcDuiker 22

Slide 22

Slide 22 text

@MarcDuiker 23

Slide 23

Slide 23 text

@MarcDuiker

Slide 24

Slide 24 text

@MarcDuiker

Slide 25

Slide 25 text

@MarcDuiker Task on backlog Work started Work completed

Slide 26

Slide 26 text

@MarcDuiker 29 https://www.atlassian.com/incident-management/kpis/common-metrics

Slide 27

Slide 27 text

@MarcDuiker 30 https://www.atlassian.com/incident-management/kpis/common-metrics

Slide 28

Slide 28 text

@MarcDuiker https://www.atlassian.com/incident-management/kpis/common-metrics

Slide 29

Slide 29 text

@MarcDuiker 32

Slide 30

Slide 30 text

@MarcDuiker 33

Slide 31

Slide 31 text

@MarcDuiker 35 Caused by the nature of the (business) problem. Can’t be easily reduced. Caused by decisions we make related to architecture, frameworks, packages, code style etc. Can be reduced. https://en.wikipedia.org/wiki/Programming_complexity

Slide 32

Slide 32 text

@MarcDuiker 36 https://en.wikipedia.org/wiki/Programming_complexity Caused by decisions we make related to architecture, frameworks, packages, code style etc. Can be reduced. Caused by the nature of the (business) problem. Can’t be easily reduced.

Slide 33

Slide 33 text

@MarcDuiker 37

Slide 34

Slide 34 text

@MarcDuiker 38

Slide 35

Slide 35 text

@MarcDuiker 40

Slide 36

Slide 36 text

@MarcDuiker 41

Slide 37

Slide 37 text

@MarcDuiker 42

Slide 38

Slide 38 text

@MarcDuiker 45

Slide 39

Slide 39 text

@MarcDuiker 46

Slide 40

Slide 40 text

@MarcDuiker 47

Slide 41

Slide 41 text

@MarcDuiker 48

Slide 42

Slide 42 text

@MarcDuiker 49 Domain Bounded Context Bounded Context Bounded Context Bounded Context https://thedomaindrivendesign.io/bounded-context/

Slide 43

Slide 43 text

@MarcDuiker 50 Ecommerce Product Catalog Inventory Billing Shopping Basket https://thedomaindrivendesign.io/bounded-context/

Slide 44

Slide 44 text

@MarcDuiker “Ubiquitous language identifies the terms and concepts within a bounded context that are unambiguous and agreed upon by all stakeholders.” https://thedomaindrivendesign.io/what-is-strategic-design

Slide 45

Slide 45 text

@MarcDuiker 52 Banking Context Ecommerce Context https://thedomaindrivendesign.io/what-is-strategic-design

Slide 46

Slide 46 text

@MarcDuiker 53

Slide 47

Slide 47 text

@MarcDuiker 54

Slide 48

Slide 48 text

@MarcDuiker “Resilience is the ability to provide and maintain an acceptable level of service in the face of faults and challenges to normal operation.” https://en.wikipedia.org/wiki/Resilience_(network)

Slide 49

Slide 49 text

@MarcDuiker

Slide 50

Slide 50 text

@MarcDuiker https://docs.microsoft.com/en-us/azure/architecture/patterns/

Slide 51

Slide 51 text

@MarcDuiker 60

Slide 52

Slide 52 text

@MarcDuiker 61

Slide 53

Slide 53 text

@MarcDuiker 62 Function App B Function App A Queue Storage

Slide 54

Slide 54 text

@MarcDuiker 63

Slide 55

Slide 55 text

@MarcDuiker 64 Increase number of (virtual) machines Increase CPU / memory of one machine

Slide 56

Slide 56 text

@MarcDuiker 66

Slide 57

Slide 57 text

@MarcDuiker

Slide 58

Slide 58 text

@MarcDuiker 68 Fan out Fan out No fan out No fan out

Slide 59

Slide 59 text

@MarcDuiker 69 Fan out Fan out No fan out No fan out https://docs.microsoft.com/en-us/azure/azure-functions/functions-scale#scale Use dedicated resource to its fullest

Slide 60

Slide 60 text

@MarcDuiker 70 Fan out Fan out No fan out No fan out https://docs.microsoft.com/en-us/azure/azure-functions/functions-scale#scale Use higher tier / sku Use regular tier / sku

Slide 61

Slide 61 text

@MarcDuiker 74 Ask yourself these questions before adding any code: - Do *I* need to write this? - Is this a good fit with the rest of the app? - What is the impact regarding resilience/scalability of the app?

Slide 62

Slide 62 text

@MarcDuiker 75 https://quest.ably.dev/

Slide 63

Slide 63 text

@MarcDuiker 76 Twitter: @marcduiker YouTube: http://bit.ly/marc-serverless Ably Discord: https://discord.gg/q89gDHZcBK