Cloud - 3 scénarios multi-providers IaaS, cloud native, serverless

Cloud - 3 scénarios multi-providers IaaS, Cloud Native et Serverless

Transcript

1. #capitoledulibre ☁ Scénarios multi-providers, #IaaS, #CloudNativeApps & #serverless pour une abstraction totale Adrien Blind, Laurent Grangeau, Ludovic Piot
2. Nous allons vous parler de… • Pourquoi faire du multi-providers dans le ☁ • 3 manières différentes de se reposer sur plusieurs plateformes de ☁ public − #IaaS : une architecture gérée entièrement − #Cloud Native Languages avec Pulumi − #Serverless : l’abstraction totale
3. Avec, dans le désordre… Adrien Blind @AdrienBlind Dataops evangelist, Docker Captain Ludovic Piot @lpiot Resp. de l’offre DevOps/Cloud Laurent Grangeau @laurentgrangeau Cloud Solution Architect, Azure MVP
4. #1 Infrastructure-as-a-Service Managing our own infrastructure
5. Dockercoin architecture RNG Worker Hasher Redis WebUI 1. Request random bytes 2. Return random bytes 3. Push random bytes 4. Push byte hash IF starts with 0
6. Architecture Incoming trafic GCE instance AWS instance
7. #2 Cloud Native Languages Deliver an hybrid app programmatically by leveraging on various cloud providers
8. Objective My App Challenge is to deliver distributed apps leveraging on various managed services... Containerized services
9. Objective My App Challenge is to deliver distributed apps leveraging on various managed services... Object Storage DBaaS Cache Put your managed service here Containerized services Serverless Functions Distributed Queues
10. Objective My App ...which may be delivered by various backends
11. New challenges raised
12. New challenges raised • Describe completely at once, your app and underlying managed services (remind, docker & K8S only deal with containers) • Be able to provision this app a first time and then manage the rest of its lifecycle (update, delete...)
13. Here (may) comes Cloud Native App Bundle
14. Rise of the Cloud Native Languages • Up to there, app/infra provisioning remained quite isolated from each other • Infra-as-code was more DSL oriented. But who likes yaml? « Je conchie yaml » Ludovic, checking a demo the 14th of may, 23:09. • Now real infra-as-code: traditional programmatic languages used to depict & provision your app • Various benefits ◦ Easier to understand, more dev centric ◦ Better density: “from 25K DSL lines to 500 lines of code” ? ◦ Apply more easily craftsmanship practices, easier testing, etc. • Most of all, make app & infra really converging, which is at heart of cloud native apps
15. Let’s discover Pulumi together • Imagined by Devs. For Devs. • Publicly announced in june 2018 • Enable to develop in Python, Go, Node.js, Typescript languages • Supports AWS / Azure / Google Cloud / Kubernetes & more ◦ Leverages on Terraform to address public cloud
16. #1 Create an S3 bucket From Pulumi examples repo
17. #2 Let’s hybridate managed services From Pulumi examples repo
18. #3 Let’s abstract (& commoditize) cloud vendors • Now let’s hide cloud vendor specific implementation with Pulumi cloud framework (Live demo)
19. Impact on app delivery & architecture Delivery • More than a DevOps guy in a feature team, you now need dev guys specialized in Ops stuff • Could contribue to spread the (very bad) idea that we no longer need Ops Architecture • Dev & Ops stuff complete intrication: you can no longer isolate infra/platform provisionning vs app execution • Rebound effect: it could enable to write new kind of apps popping their infrastructure assets on the fly. Ex you could write data processing pipelines popping the underlying jobs
20. Final words • Pulumi enables to ◦ Facilitates use of cloud managed services ◦ Hybridate services ◦ Create an abstraction layer on top of cloud vendors ◦ Consider infrastructure as part of the app code • Pulumi is not the only one on the market: check out Ballerina, or Meta Particle for instance
21. #3 Serverless Total abstraction
22. Proposition ▪ Create a static website with VueJS ▪ Deploy frontend to Azure ▪ Create a backend with Serverless.com framework ▪ Deploy backend to AWS ▪ Add a CI/CD pipeline ▪ Explore others hosting services (Netlify) #3 - le Serverless
23. Static website with VueJS (Azure) #3 - le Serverless
24. #3 - le Serverless
25. #3 - le Serverless
26. #3 - le Serverless
27. #3 - le Serverless
28. Deploy to Azure (VSCode) #3 - le Serverless
29. #3 - le Serverless
30. Backend with Serverless.com (AWS) #3 - le Serverless
31. #3 - le Serverless
32. #3 - le Serverless
33. #3 - le Serverless
34. Invoke and logging #3 - le Serverless
35. #3 - le Serverless
36. #3 - le Serverless
37. Add HTTP endpoint #3 - le Serverless
38. #3 - le Serverless
39. #3 - le Serverless
40. Call lambda functions with VueJS #3 - le Serverless
41. #3 - le Serverless
42. #3 - le Serverless
43. CORS #3 - le Serverless
44. #3 - le Serverless
45. Custom domains for URL invocation #3 - le Serverless
46. #3 - le Serverless
47. #3 - le Serverless
48. #3 - le Serverless
49. #3 - le Serverless
50. #3 - le Serverless
51. #3 - le Serverless
52. #3 - le Serverless
53. #3 - le Serverless
54. Persist with MongoDB Atlas (GCP) #3 - le Serverless
55. CI/CD pipeline (Azure) #3 - le Serverless
56. #3 - le Serverless
57. Netlify #3 - le Serverless
58. #3 - le Serverless
59. #3 - le Serverless
60. Questions ?
61. ROTI