Serverless DevOps - Chicago Code Camp 2018
•Transferir como PPTX, PDF•
0 gostou•129 visualizações
A presentation on how to approach Serverless DevOps on Azure
Recomendados
Recomendados
Mais conteúdo relacionado
Semelhante a Serverless DevOps - Chicago Code Camp 2018
Semelhante a Serverless DevOps - Chicago Code Camp 2018 (20)
Mais de Sasha Rosenbaum
Último
Último (20)
Serverless DevOps - Chicago Code Camp 2018
- 1. Serverless DevOps on Azure Platform SASHA ROSENBAUM
- 2. Who Am I?
- 3. Serverless
- 4. Serverless Code Events + dataAzure Functions
- 5. Triggers and Bindings Type 1.x 2.x Trigger Input Output Blob Storage ✔ ✔ 1 ✔ ✔ ✔ Cosmos DB ✔ ✔ ✔ ✔ ✔ Event Grid ✔ ✔ ✔ Event Hubs ✔ ✔ ✔ ✔ External File 2 ✔ ✔ ✔ External Table 2 ✔ ✔ ✔ HTTP ✔ ✔ 1 ✔ ✔ Type 1.x 2.x Trigger Input Output Microsoft Graph Excel tables ✔ ✔ ✔ Microsoft Graph OneDrive files ✔ ✔ ✔ Microsoft Graph Outlook email ✔ ✔ Microsoft Graph Events ✔ ✔ ✔ ✔ Microsoft Graph Auth tokens ✔ ✔
- 6. Triggers and Bindings Type 1.x 2.x Trigger Input Output Mobile Apps ✔ ✔ ✔ ✔ Notification Hubs ✔ ✔ Queue storage ✔ ✔ 1 ✔ ✔ SendGrid ✔ ✔ ✔ Service Bus ✔ ✔ ✔ ✔ Table storage ✔ ✔ 1 Type 1.x 2.x Trigger Input Output Timer ✔ ✔ ✔ Twilio ✔ ✔ ✔ Webhooks ✔ ✔ ✔
- 8. No Servers = No Ops
- 9. My code always works
- 11. DevOps CI/CD
- 12. Develop + Test Plan + Track Monitor + Learn Release Development Production
- 15. Function Best Practices Stateless Idempotent Asynchronous Durable Functions and Queues Batching
- 16. Durable Functions - Chaining
- 17. Durable Functions – Fan out/fan in
- 18. Functions - Things to Remember Cold start Execution time limit Concurrency Throttling Quotas Downstream components Experimental languages C# script
- 19. Functions - Things to Remember Always load test!!!
- 20. Questions?
Notas do Editor
- Serverless computing is an execution model in which the customer only manages the code, and the vendor manages the allocation of compute resources. It is also known as Functions as a Service, which is actually a better name for it. In Serverless, your code is triggered based on events, and it executes to produce the desired results.
- 1 In 2.x, all bindings except HTTP, Timer, and Azure Storage must be registered. See Register binding extensions. 2 Experimental — not supported and might be abandoned in the future.
- Serverless computing is an execution model in which the customer only manages the code, and the vendor manages the allocation of compute resources. It is also known as Functions as a Service, which is actually a better name for it. In Serverless, your code is triggered based on events, and it executes to produce the desired results.
- I only care about milk, and it is so much cheaper, and so much less maintenance!
- I don’t know about you, but my code always works! It’s perfect from the beginning It needs no testing It needs no monitoring I anticipate all the client requests for changes and implement them in version one Not…
- Oh no, we have a problem here!
- Fortunately, the problem has already been solved
- There is a plethora of great tools out there
- When Microsoft came into this market, we were not the first comer, and thus we had the second comer advantage. The first thing we did is go to the developers and ask them what they like and dislike about Serverless And the #1 response was – developer experience
- Function chaining refers to the pattern of executing a sequence of functions in a particular order. Often the output of one function needs to be applied to the input of another function.
- Fan-out/fan-in refers to the pattern of executing multiple functions in parallel, and then waiting for all to finish. Often some aggregation work is done on results returned from the functions. There are 3 more patterns in durable functions: Async HTTP APIs Have a long-running action triggered by an HTTP call, and then redirecting the client to a status endpoint that they can poll to learn when the operation completes. Monitoring Using Durable Functions, multiple monitors that observe arbitrary endpoints can be created in a few lines of code. Human interaction The orchestrator function would use a durable timer to request approval and escalate in case of timeout.