1. Тема доклада
Тема доклада
Тема доклада
KYIV 2019
Stas Lebedenko
Practical serverless use cases in Azure.
.NET CONFERENCE #1 IN UKRAINE

2. The ultimate goal is to
minimize the lifetime cost of
the system and to maximize
programmer productivity.
@martinfowler

3. ● Azure Functions
● Azure API Management
● Azure Logic Apps
● Azure SQL Serverless
● Azure Event Grid
● KEDA - Kubernetes-based
event-driven autoscale

4. Most popular use cases.

5. Functions cold start

6. Usage with classic
applications

7. The catch with legacy
01 | Cannot handle spike loads.
02 | Caching is a must.
03 | Rate limit via API Facades.
04 | Adjust outgoing throughput.
05 | Limit scalability.
06 | Tune connection pool of SQL Server.

8. Client applications
● Implement retry.
● Track connection issues.
● Handle 50x and 40x.
● Use additional responses
429 - Too many requests
420 - Enhance your calm

10. Serverless API facades
Azure Functions Proxy Azure API Management
VS

11. Serverless Web App

12. Serverless API

13. Stateless actors

14. Event-driven
applications

15. Durable functions
01 | Based on Durable Task Framework.
02 | Stateful coordination.
03 | Partially in preview.
04 | Orchestrator function.
05 | Entity function.
06 | Ideal for complex
Coordinated pipelines.

16. IoT Hub message pipelines

17. Event processing pipelines

18. ETL via Fan-in => Fan-out

19. Big Data pipelines

20. Durable orchestration

21. Serverless best
practices and pitfalls

22. Best practices
01 | Keep function small and stateless.
02 | Control connection limits.
03 | Design for failure and use throttling.
04 | Avoid long runs and direct chaining.
05 | Use HttpClient via static.
06 | Use scalable storages.
07 | Build communications via queues and hubs.

23. Pitfalls
01 | Consumption compute slow
02 | Scale-out have limits.
03 | Bad fit with legacy.
04 | Cold start.
06 | Cloud vendor lock-in.
07 | Failure at scale.

24. Know your limits
01 | Functions connections limits.
02 | Processing time limit.
03 | External rate limits.
04 | Scale-out limit.
05 | ACU per instance limit.
06 | Storage limit.

25. SECURITY ● Function code auth.
● 5 App Service options.
● No custom OIDC option.
● CSP, CORS settings.
● Azure Managed Identity.
● VNet only in Premium
plan.

26. Just a few tricks
Premium scaler

27. Massive scale increase
probability of the
massive failure.

28. ● Consumption plan is cheap
● Billing estimation is
complicated.
● Cheapest possible ETL.
● Long running functions
with poor design will result
in excessive cost.
● Vulnerable for Denial-of-
wallet attacks.

29. Cloud-agnostic
serverless

30. Any platform, any cloud?
01 | Vendor lock-in problem.
02 | Multicloud is a tech debt.
03 | Consider local run option.
04 | Storage is the real problem.
05 | Think in terms of code.
06 | Estimate multi cloud.

31. Pulumi framework

32. Serverless framework

33. Wrap-up

34. Demo. Your rate prediction.

35. Ask Zoltar

36. Keep up with technology

37. Questions?
Linked IN Twitter