Download as PDF, PPTX
![@cdavisafc
CLOUD-NATIVE APP
STATELESSNESS
ROUTER
APP
(INSTANCE 1)
ValidTokens:
[UserToken]
/login
token=UserToken
token=UserToken](https://image.slidesharecdn.com/cloudnativearchitecturedoes2017-171115061140/75/Cloud-Native-Architectures-for-Devops-15-2048.jpg)
![@cdavisafc
CLOUD-NATIVE APP
STATELESSNESS
ROUTER
APP
(INSTANCE 1)
ValidTokens:
[UserToken]
/login
token=UserToken
token=UserToken
APP
(INSTANCE 2)
ValidTokens: []](https://image.slidesharecdn.com/cloudnativearchitecturedoes2017-171115061140/75/Cloud-Native-Architectures-for-Devops-16-2048.jpg)
![@cdavisafc
CLOUD-NATIVE APP
STATELESSNESS
ROUTER
APP
(INSTANCE 1)
ValidTokens:
[UserToken]
/login
token=UserToken
token=UserToken
APP
(INSTANCE 2)
Unauthorized ValidTokens: []
token=UserToken](https://image.slidesharecdn.com/cloudnativearchitecturedoes2017-171115061140/75/Cloud-Native-Architectures-for-Devops-17-2048.jpg)
![@cdavisafc
CLOUD-NATIVE APP
STATELESSNESS
▸ Do NOT use sticky sessions!
▸ Eventually (and sooner than you
think!) the instance you are sticky to
will disappear
▸ Do make your instances
completely stateless
ROUTER
APP
(INSTANCE 1)
ValidTokens:
[UserToken]
/login
token=UserToken
token=UserToken
APP
(INSTANCE 2)
Unauthorized ValidTokens: []
token=UserToken](https://image.slidesharecdn.com/cloudnativearchitecturedoes2017-171115061140/75/Cloud-Native-Architectures-for-Devops-18-2048.jpg)
![@cdavisafc
CLOUD-NATIVE APP
STATELESSNESS
▸ Do NOT use sticky sessions!
▸ Eventually (and sooner than you
think!) the instance you are sticky to
will disappear
▸ Do make your instances
completely stateless
▸ Externalize state
ROUTER
APP
(INSTANCE 1)
ValidTokens:
[UserToken]
token=UserToken
token=UserToken
APP
(INSTANCE 2)
token=UserToken
STATE
STORE](https://image.slidesharecdn.com/cloudnativearchitecturedoes2017-171115061140/75/Cloud-Native-Architectures-for-Devops-19-2048.jpg)
Uploaded bycornelia davis
Cloud Native Architectures for Devops
The document discusses cloud-native architecture, emphasizing its benefits such as scalability, resilience, and statelessness. Key concepts include service discovery, versioned services, and externalized configuration to enhance application autonomy and adaptability in a distributed environment. Strategies for data management, including breaking the data monolith and implementing caching, are also highlighted to support effective microservice operations.
More Related Content
Similar to Cloud Native Architectures for Devops
Cloud Native Architectures for Devops
- 1. @cdavisafc CLOUD-NATIVE DESIGNING CHANGE-TOLERANT SOFTWARE CorneliaDavis, Sr. Director of Technology, Pivotal
- 2. @cdavisafc FROM THE 2017STATE OF DEVOPS REPORT
- 3.
- 4. @cdavisafc CLOUD-NATIVE = LOOSELYCOUPLED RUNNING IN THE CLOUD Cloud is where you compute Cloud-native is how.
- 5. @cdavisafc TEXT ME? Developer (wasn’t Ops) Webarchitectures for >10 years Cloud-native for 5 years Cloud Foundry for 5 years More recently
- 6. @cdavisafc TEXT A Seattle technologycompany hosts applications for thousands of major corporations
- 7. @cdavisafc TEXT Major Outage on20 September 2015 Airbnb, Nest, IMDB and many more experienced downtime … Including Netflix Outage lasted 5+ hours “brief availability blip” experienced a
- 8. @cdavisafc CLOUD-NATIVE SERVICE LET’S TALKABOUT AUTONOMY A major benefit of cloud-native architectures is independent: ▸ Application Scaling ▸ Team Scaling ▸ Development Cycles ▸ Experimentation ▸ Resilience
- 9. @cdavisafc CLOUD-NATIVE ARCHITECTURES ▸ Cloud-nativeApps ▸ Scale out ▸ Statelessness ▸ Externalize configuration ▸ Implications from changes in the application lifecycle ▸ Versioned services ▸ Service Discovery ▸ Distributed tracing ▸ Retries ▸ Cloud-native Data ▸ Breaking the Data monolith ▸ Data APIs ▸ Caching ▸ Polyglot Persistence ▸ Event sourcing
- 10.
- 11. @cdavisafc CLOUD-NATIVE APP SCALE HORIZONTALLY APPAPP APP APP APP
- 12. @cdavisafc CLOUD-NATIVE APP APP APP APP APP APP APPAPP APP APP APP APP APP APP APP APP SCALE HORIZONTALLY APP APP APP APP APP
- 13. @cdavisafc CLOUD-NATIVE APP APPAPP APPAPPAPPAPPAPP APPAPPAPPAPPAPP APP APP APP APP APPAPP APP APP APP APP APP APP APP SCALE HORIZONTALLY APP APP APP APP APP
- 14. @cdavisafc CLOUD-NATIVE APP APPAPP APPAPPAPPAPPAPP APPAPPAPPAPPAPP APP APP APP APP APPAPP APP APP APP APP APP APP APP SCALE HORIZONTALLY ▸ Need an abstraction to treat set of instances as one logical unit ▸ Load Balancing - DNS? Something else? ▸ Dynamic!!! ▸ IP Addresses of instances always changing APP APP APP APP APP ROUTER ROUTER
- 15.
- 16.
- 17. @cdavisafc CLOUD-NATIVE APP STATELESSNESS ROUTER APP (INSTANCE 1) ValidTokens: [UserToken] /login token=UserToken token=UserToken APP (INSTANCE2) Unauthorized ValidTokens: [] token=UserToken
- 18. @cdavisafc CLOUD-NATIVE APP STATELESSNESS ▸ DoNOT use sticky sessions! ▸ Eventually (and sooner than you think!) the instance you are sticky to will disappear ▸ Do make your instances completely stateless ROUTER APP (INSTANCE 1) ValidTokens: [UserToken] /login token=UserToken token=UserToken APP (INSTANCE 2) Unauthorized ValidTokens: [] token=UserToken
- 19. @cdavisafc CLOUD-NATIVE APP STATELESSNESS ▸ DoNOT use sticky sessions! ▸ Eventually (and sooner than you think!) the instance you are sticky to will disappear ▸ Do make your instances completely stateless ▸ Externalize state ROUTER APP (INSTANCE 1) ValidTokens: [UserToken] token=UserToken token=UserToken APP (INSTANCE 2) token=UserToken STATE STORE
- 20. @cdavisafc CLOUD-NATIVE APP APP CONFIGURATION ▸Property Files are the abstraction used to externalize configuration ▸ They do not hold actual values! ▸ Values coming from the environment are supplied via environment variables ▸ Other configuration is controlled just like source code and injected RUNTIME CONTEXT WHERE CONFIGURATION PARAMETERS ARE DEFINED IN ENVIRONMENT VARIABLES PROPERTY FILE(S) DEFINE THE CONFIGURATION PARAMETERS AND DEFAULT VALUES hostIp= ${CF_INSTANCE_IP} specialization= ${SPECIALIZATION: Science} APP CODE THAT REFERENCES THE CONFIGURATION PARAMETERS DEFINED IN THE PROPERTY FILE public class HelloController { @Value("${hostIp}") private String hostIp; @Value("${specialization}") private String specialization; ... } SYSTEM PROPERTIES PROVIDED BY THE RUNTIME ENVIRONMENT, VIA ENVIRONMENT VARIABLES CF_INSTANCE_IP=10.10.148.29
- 21. @cdavisafc CLOUD-NATIVE APP APP CONFIGURATION ▸Other configuration is controlled just like source code and injected RUNTIME CONTEXT WHERE CONFIGURATION PARAMETERS ARE DEFINED IN ENVIRONMENT VARIABLES PROPERTY FILE(S) DEFINE THE CONFIGURATION PARAMETERS AND DEFAULT VALUES hostIp= ${CF_INSTANCE_IP} specialization= ${SPECIALIZATION: Science} APP CODE THAT REFERENCES THE CONFIGURATION PARAMETERS DEFINED IN THE PROPERTY FILE public class HelloController { @Value("${hostIp}") private String hostIp; @Value("${specialization}") private String specialization; ... } SYSTEM PROPERTIES PROVIDED BY THE RUNTIME ENVIRONMENT, VIA ENVIRONMENT VARIABLES CF_INSTANCE_IP=10.10.148.29 APP PROPERTIES STORED AND VERSIONED IN A REPOSITORY SUCH AS GIT specialization =Sports CONFIG SERVER ROLE IS TO INJECT MANAGED APP PROPERTIES INTO THE APP
- 22. @cdavisafc CLOUD-NATIVE APP APPLICATION LIFECYCLE ▸Application lifecycle events have rippling effects through the collective INVOICE APP ordersvcIP =10.24.1.35 ORDER SERVICE APP 10.24.1.3510.24.63.116
- 23. @cdavisafc CLOUD-NATIVE APP APPLICATION LIFECYCLE ▸Application lifecycle events have rippling effects through the collective ▸ The application must broadcast lifecycle change events ▸ (Note: I strongly recommend you use a framework to help you with this!) ▸ And an app must be able to absorb that configuration at the right time (run time?) INVOICE APP ordersvcIP =10.24.1.35 ORDER SERVICE APP Some “magic” happens 10.24.63.116 Here I am! IP Address: 10.24.63.116 Version: 3.4.239 … I’ll adapt to these changes! Orders Service new IP: 10.24.63.116
- 24. @cdavisafc CLOUD-NATIVE SERVICE VERSIONED SERVICES ▸Use Semantic Versioning ▸ major.minor.patch ▸ Use Blue/Green deploys ▸ Deployments needn’t be replacements ▸ Powerful lever in making deployments a non-event SERVICE APP SERVICE APP APP SERVICE APP APP … AND PARALLEL DEPLOYS
- 25. @cdavisafc CLOUD-NATIVE SERVICE VERSIONED SERVICES ▸Use Semantic Versioning ▸ major.minor.patch ▸ Use Blue/Green deploys ▸ Deployments needn’t be replacements ▸ Powerful lever in making deployments a non-event SERVICE APP SERVICE APP APP SERVICE APP APP … AND PARALLEL DEPLOYS SERVICE APP 1.0.0 2.0.0
- 26. @cdavisafc CLOUD-NATIVE SERVICE SERVICE DISCOVERY ▸Let’s dig into the “magic” (it’s not really magic) INVOICE APP orderSvcCoords... ORDER SERVICE APP 10.24.63.116 Here I am! IP Address: 10.24.63.116 Version: 3.4.239 … I’ll adapt to these changes! Orders Service new IP: 10.24.63.116 Some “magic” happens
- 27. @cdavisafc CLOUD-NATIVE SERVICE SERVICE DISCOVERY ▸Dynamic Router maintains routing table ▸ Messaging pattern to decouple service from router ▸ Must handle lost broadcast messages ▸ Request pass through router INVOICE APP orderSvcCoords =orderSvc.example.com ORDER SERVICE APP 10.24.63.116 Here I am! IP Address: 10.24.63.116 Version: 3.4.239 … ROUTER OrderService: 10.24.63.116, … CustomerService: 10.24.3.1, …
- 28. @cdavisafc CLOUD-NATIVE SERVICE SERVICE DISCOVERY ▸Dynamic Router maintains routing table ▸ Messaging pattern to decouple service from router ▸ Must handle lost broadcast messages ▸ Request pass through router INVOICE APP orderSvcCoords =10.24.1.13 ORDER SERVICE APP 10.24.63.116 Here I am! IP Address: 10.24.63.116 Version: 3.4.239 … SERVICE DISCOVERY SERVER OrderService: 10.24.63.116, … CustomerService: 10.24.3.1, … ORDER SERVICE APP 10.24.1.13 I’ll adapt to these changes! Orders Service new IP: 10.24.63.116
- 29. @cdavisafc CLOUD-NATIVE SERVICE SERVICE DISCOVERY ▸Dynamic Router maintains routing table ▸ Messaging pattern to decouple service from router ▸ Must handle lost broadcast messages ▸ Request pass through router INVOICE APP orderSvcCoords =10.24.63.116 ORDER SERVICE APP 10.24.63.116 Here I am! IP Address: 10.24.63.116 Version: 3.4.239 … SERVICE DISCOVERY SERVER OrderService: 10.24.63.116, … CustomerService: 10.24.3.1, … ORDER SERVICE APP 10.24.1.13 I’ll adapt to these changes! Orders Service new IP: 10.24.63.116
- 30. @cdavisafc CLOUD-NATIVE SERVICE CIRCUIT BREAKERS ▸You’ve probably seen this picture… https://martinfowler.com/bliki/CircuitBreaker.html
- 31. @cdavisafc CLOUD-NATIVE SERVICE CIRCUIT BREAKERS ▸You’ve probably seen this picture… ▸ … but why do we need circuit breakers in the first place https://martinfowler.com/bliki/CircuitBreaker.html
- 32. @cdavisafc CLOUD-NATIVE SERVICE RETRIES ▸ #1Fallacy of Distributed Computing: https://en.wikipedia.org/wiki/Fallacies_of_distributed_computing
- 33. @cdavisafc CLOUD-NATIVE SERVICE RETRIES ▸ #1Fallacy of Distributed Computing: The Network is Reliable https://en.wikipedia.org/wiki/Fallacies_of_distributed_computing
- 34. @cdavisafc CLOUD-NATIVE SERVICE RETRIES ▸ #1Fallacy of Distributed Computing: The Network is Reliable It's not. https://en.wikipedia.org/wiki/Fallacies_of_distributed_computing
- 35. @cdavisafc CLOUD-NATIVE SERVICE RETRIES CLIENT SERVICE ▸ Clientmust consider failure ▸ Decide on fall-back behavior ▸ Likely including retries ▸ But then we need to handle downstream consequences of these (retry) behaviors Timeouts? If we don’t hear back, try again
- 36. @cdavisafc CLOUD-NATIVE SERVICE CIRCUIT BREAKERS ▸This is your protection against DDOSing yourself https://martinfowler.com/bliki/CircuitBreaker.html
- 37.
- 38.
- 39. @cdavisafc CLOUD-NATIVE SERVICE DISTRIBUTED TRACING ▸App must look for and leave tracers ▸ Use a framework to help you do this!!! ▸ Tools can then read and correlate logs SERVICE APP SERVICE APP APP SERVICE APP SERVICE APP SERVICE APP
- 40.
- 41. @cdavisafc CLOUD-NATIVE DATA WE ARELOOSELY COUPLED!
- 42.
- 43. @cdavisafc CLOUD-NATIVE DATA THIS ISNOT CLOUD-NATIVE DATA
- 44. @cdavisafc CLOUD-NATIVE DATA DATA APIS(SERVICES) ▸ Microservices do not access data layer directly ▸ Except for those that implement the data API ▸ A surface area to: ▸ Implement access control ▸ Implement throttling ▸ Perform logging ▸ Other policies…
- 45. @cdavisafc CLOUD-NATIVE DATA ANTI-PATTERN: DATAAPIS THAT JUST PROXY
- 46. @cdavisafc CLOUD-NATIVE DATA EVERY MICROSERVICENEEDS A CACHE
- 47. @cdavisafc CLOUD-NATIVE DATA “Caching atNetflix: The Hidden Microservice” https://www.youtube.com/watch?v=Rzdxgx3RC0Q
- 48. @cdavisafc CLOUD-NATIVE DATA VERSIONED DATAAPIS (SERVICES) ▸ We are already familiar with versioned microservices… V1 V2
- 49. @cdavisafc CLOUD-NATIVE DATA VERSIONED DATAAPIS (SERVICES) ▸ We are already familiar with versioned microservices… … and V1 V2 PARALLEL DEPLOYS
- 50. @cdavisafc TEXT We used to: AUTONOMY! V2 V1 Allclients moved in lockstep Or another: V1.0 V1.1 V2.0 Now, one option: V1.0 V1.1 V2.0 V2.1 Or even: V1.0 V2.0 (!) Think Unified Log
- 51. @cdavisafc CLOUD-NATIVE DATA DATABASE PERMICROSERVICES
- 52. @cdavisafc CLOUD-NATIVE DATA DATABASE PERMICROSERVICES ▸ Supports Polyglot persistence ▸ Independent availability, backup/restore, access patterns, etc.
- 53.
- 54. @cdavisafc CLOUD-NATIVE DATA CLIENT SIDEJOIN My Connections API Posts API New from Network API
- 55.
- 56. @cdavisafc CLOUD-NATIVE DATA INDEPENDENT DATABASES- SHARED ENTITIES ▸ We’ve started to break up the data monolith ▸ BUT our data integration “strategy” is rather brittle and bespoke ▸ How are changes to data in one bounded context reflected in the other? Sales Support ?
- 57.
- 59.
- 60.
- 61. @cdavisafc CLOUD-NATIVE DATA SOURCE OFTRUTH My Connections API Posts API New from Network API Unified Log
- 62. @cdavisafc CLOUD-NATIVE ARCHITECTURES ▸ Cloud-nativeApps ▸ Scale out ▸ Statelessness ▸ Externalize configuration ▸ Implications from changes in the application lifecycle ▸ Versioned services ▸ Service Discovery ▸ Distributed tracing ▸ Retries ▸ Cloud-native Data ▸ Breaking the Data monolith ▸ Data APIs ▸ Caching ▸ Polyglot Persistence ▸ Event sourcing
- 63. @cdavisafc REFERENCES ▸ Scott Mansfieldof the Netflix Caching team: ▸ Public video: https://www.youtube.com/watch? v=Rzdxgx3RC0Q&t=205s ▸ Safari books online video (slightly expanded): https:// www.safaribooksonline.com/library/view/oreilly- software-architecture/9781491976142/ video289789.html ▸ Slideshare: https://www.slideshare.net/ScottMansfield3/ application-caching-the-hidden-microservice ▸ Netflix on the “brief availability blip”: https://medium.com/ netflix-techblog/chaos-engineering- upgraded-878d341f15fa
- 64.