Serverless の自動回復と自動化のためのアーキテクチャ
•Download as PPTX, PDF•
4 likes•4,642 views
NoOps Meetup で発表した内容です。Serverless の自動化のためのアーキテクチャとそのコード、自動回復のためのアーキテクチャのポイント、そして分散トレーシングの実装をするとどいう言うことが起きるかという話です。
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Serverless の自動回復と自動化のためのアーキテクチャ
Similar to Serverless の自動回復と自動化のためのアーキテクチャ (20)
More from Tsuyoshi Ushio
More from Tsuyoshi Ushio (20)
Recently uploaded
Recently uploaded (7)
Serverless の自動回復と自動化のためのアーキテクチャ
- 1. Serverless の自動回復と 自動化のためのアーキテクチャ 牛尾 剛 Microsoft Corporation CSE - EEST Senior Software Engineer
- 6. オンプレミス IaaS (一般的な) PaaS サーバレス (これも PaaS の一種/FaaS) クラウド ハードウェア OS ランタイム アプリ (関数呼び出し) 関数 ハードウェア OS ランタイム アプリ (関数呼び出し) 関数 ハードウェア OS ランタイム アプリ (関数呼び出し) 関数 ハードウェア OS ランタイム アプリ (関数呼び出し) 関数 @chomado 作
- 7. [FunctionName("Function1")] public static async Task<IActionResult> Run( [HttpTrigger(AuthorizationLevel.Function, "get", "post", Route = null)] dynamic obj, [CosmosDB("databaseName", "collectionName",Id = "abc", ConnectionStringSetting = "SomeConnection")] dynamic input, [Queue("myqueue", Connection = "ConnectionString")] IAsyncCollector<string> outputQueue, ILogger log) { log.LogInformation("C# HTTP trigger function processed a request."); var output = $"{obj.Name}: id: abc value: {input.value}"; await outputQueue.AddAsync(output); return (ActionResult)new OkObjectResult($"Hello, {obj.Name}"); }
- 9. 翻訳超めんどくさい問 題
- 10. 普段の解法 この筋肉で 解決
- 14. 自動化のためのアーキテク チャ
- 16. テストピラミッド
- 17. ユニットテストの重要性
- 18. 良いユニットテストとは
- 19. Hexagonal Architecture Http CosmosDB Azure Search Storage Account Azure Functions Model Domain Application Layer Model
- 20. Hexagonal Architecture Http CosmosDB Azure Search Storage Account Azure Functions Model Domain Application Layer Model
- 21. Strategy for Azure Functions Model Domain Model
- 23. DI (Dependency Injection) and Wrapper
- 24. ３つのタイプのユニットテスト
- 25. テスト可能な設計のための Tips Respoitory Pattern with ASP.NET Core https://docs.microsoft.com/en-us/aspnet/core/fundamentals/repository-pattern?view=aspnetcore-2.1
- 27. ブラウザ Proxy Blob (SPA) Upload Blob (画像) CosmosDB Create Car Review 01 Search
- 28. Change Feed Blob (画像) CosmosDB Car Review 02 Change Feed Check Text Text checked Rejected
- 29. Send event Car Review 03 Handle Reject Review
- 30. ややこしいね ん
- 31. 10分
- 32. 障害起こったら どうするん？
- 36. 自動回復のためのアーキテ クチャ
- 37. 自動回復のためのアーキテクチャ
- 38. 分散トレーシング
- 39. 分散トレーシングの実装
- 41. ２つの分散トレーシングプロトコル https://github.com/dotnet/corefx/blob/master/src/System.Diagnostics.DiagnosticSource/src/HttpCorrelationProtocol.md https://w3c.github.io/trace-context/#traceparent-field tsuyoshi ushio correlation 検索 Correlation with Activity with Application Insights (1) - (3)
- 42. Request Telemetry Dependency Telemetry Request Telemetry Function2 Function1 HttpRequest Queue Telemetry Id ParentId RootId Request |UEJDOAJH7eU=.3320d4ac_1. |UEJDOAJH7eU=.3320d4ac_ UEJDOAJH7eU= Dependency |UEJDOAJH7eU=.3320d4ac_1.3320d4b1_ |UEJDOAJH7eU=.3320d4ac_1. UEJDOAJH7eU= ParentId |UEJDOAJH7eU=.3320d4ac_1.3320d4b1_ Telemetr y Id ParentId RootId Request |UEJDOAJH7eU=.3320d4ac_1.3320d4 b1_3320d4b7_ |UEJDOAJH7eU=.3320d4ac_1.3320d4b1 _ UEJDOAJH7eU =
- 43. Request Telemetry Dependency Telemetry Orchestrator HttpRequest Request Telemetry HttpRequest Orchestrator Dependency Telemetry Queue Queue Request Telemetry Dependency Telemetry Activity Queue Telemetry TraceId SpanId ParentSpanId Request 93bd77f9142bea4aa194fc17ad673a8d 3ad91ae6deb7ff48 - Dependency 93bd77f9142bea4aa194fc17ad673a8d 3cb76023174d3342 3ad91ae6deb7ff48 Telemetry TraceId SpanId ParentSpanId Request 93bd77f9142bea4aa194fc17ad673a8d 285c9d6ec7291e45 3cb76023174d3342 Telemetry TraceId SpanId ParentSpanId Dependency 93bd77f9142bea4aa194fc17ad673a8d 20b980b04525c74f 285c9d6ec7291e4 5 Telemetry TraceId SpanId ParentSpanId Request 93bd77f9142bea4aa194fc17ad673a8d b7b5267e3136794b 285c9d6ec7291e45 Dependency 93bd77f9142bea4aa194fc17ad673a8d 228afc082cc2924c b7b5267e3136794 b
- 44. 分散トレーシング実装の課題
- 45. Scope of the Activity WebJobs.HostWebJobs.Extensions.DurableTask DurableTask AzureStorageOrchestrationService. LockNextTaskOrchestrationWorkItemAsync ProcessQueue AzureStorageOrchestrationService. CompleteTaskOrchestrationWorkItemAsync Send Queue TaskOrchestrationShim Execute Function DurableProto User Function ApplicationInsightsLogger Send RequestTemeletry TaskOrchestrationWorkItem / OrchestrationSession Activity Scope 02 Create Parameter Send Queue Receive Queue Activity Scope 01 DurableTaskExtension .OrchestrationMiddleWare Deletage to TaskOrchestrationShim ① ② ③ ④ ⑤ ⑥ Activity Scope 03
- 48. © 2018 Microsoft Corporation. All rights reserved. 本情報の内容（添付文書、リンク先などを含む）は、作成日時点でのものであり、予告なく変更される場合があります。
Editor's Notes
- Full abstraction of servers developers can just focus on their code—there are no distractions around server management, capacity planning, or availability. Instant, event-driven scalability Application components react to events and triggers in near real-time with virtually unlimited scalability; compute resources are used as needed. Pay-per-use Only pay for what you use: billing is typically calculated on the number of function calls, code execution time, and memory used.*
- さんかくは、線にする 処理は、右からひだりへながれる
- ３まいをまとめて、Queue地獄のページを作る 要素をへらさないといけない －＞Queueをへらすのがおおい
- https://www.pakutaso.com/
- Imagine a scenario where I have to take the output of a Function and use it as the input to call another Function. I’ll have to coordinate the chaining manually. If I have to have a function that takes some sort of event and then parallelizes it into multiple Functions, I can still do that but how will I know when all Functions have finished executing so I can aggregate the results and move on. What if I had to listen on multiple events and aggregate their outcome to determine which specific job or function to run in my application. What if I wanted to do some kind of extended monitoring on an endpoint? For example, if I were to monitor the temperature of a remote machine and take action x if the temperature were lower than a certain threshold, else do y or run job y. What if I have an API or endpoint that was running for a long time? I know Functions are short-lived but sometimes you guys put some serious load on them. Could there be a mechanism to provide status of the execution back to the client so they’re not left hanging? And lastly, what if I wanted to get some sort of human interaction in there? For example, if I am to do some sort of 2FA in the middle of my function execution but also don’t want to wait forever because sometimes people take forever to reply especially when the texts are automated. Today, I’m going to be talking about some of these problems – how you can approach them in regular FaaS? And how they can be simplified with the technology of Durable Functions.