Planet Scale Applications with Cosmos DB and Pulumi

An example of how Pulumi and Infrastructure as code help create globally-distributed applications in Azure

Transcript

1. Azure Cosmos DB and Pulumi How to Build Planet Scale Applications in Minutes
2. Application v1 2 in a single geographic location (Azure region)
3. Deployed to a single location derived from the resource group Azure Cosmos DB in Pulumi 101 3
4. Deployed to a single location derived from the resource group Azure Cosmos DB in Pulumi 101 4
5. The Function code can be defined inline inside the Pulumi program. Pulumi serializes it and produces the deployment artifact. Deployed to the single location next to the Cosmos DB account Azure Functions in Pulumi 101 5
6. The Function code can be defined inline inside the Pulumi program. Pulumi serializes it and produces the deployment artifact. Deployed to the single location next to the Cosmos DB account Azure Functions in Pulumi 101 6 Cosmos DB connection parameters are passed implicitly as the variables. Alternatively, we could set them as application settings.
7. Pulumi Up result 7
8. Global Users 8
9. Latency 9 San Francisco 133 ms Frankfurt 393 ms Hong-Kong 437 ms End-to-end response time of the application Even though the database response time is < 10ms
10. Distributed Application Around the Globe
11. Deployed to multiple configurable locations Distributed Cosmos DB 11
12. Deployed to multiple configurable locations Distributed Cosmos DB 12
13. Has Latency Improved? 13 San Francisco 128 ms Frankfurt 382 ms Hong-Kong 451 ms End-to-end response time of the application Not really…
14. Global Users 14
15. Distributed Application v1 15 in multiple geographic locations (Azure regions)
16. Deployed to multiple configurable locations Distributed Code 16
17. Profile configuration defines the routing method and DNS settings. Global DNS-based routing service Traffic Manager 17 An endpoint is created to target each region. Endpoints are connected to the targets (Azure Function Apps in this case).
18. Profile configuration defines the routing method and DNS settings. Global DNS-based routing service Traffic Manager 18 An endpoint is created to target each region. Endpoints are connected to the targets (Azure Function Apps in this case).
19. Profile configuration defines the routing method and DNS settings. Global DNS-based routing service Traffic Manager 19 An endpoint is created to target each region. Endpoints are connected to the targets (Azure Function Apps in this case).
20. Latency Improved! 20 San Francisco 133 ms Frankfurt 128 ms Hong-Kong 149 ms End-to-end response time of the application The user connects to the closest HTTP endpoint which pulls data from the local replica
21. Pattern Can we make it reusable?
22. Shopping Cart Service v1 22 Docker + Azure Container Instances
23. Pricing Engine Service v1 23 Virtual Machines
24. Pattern v1 24 An abstraction that fits multiple use cases
25. A reusable GlobalApp component creates the common infrastructure including a global Cosmos DB account, Traffic Manager, etc. A custom Pulumi component Global App 25 A factory function creates the infrastructure for a specific use case: both global and regional resources.
26. A reusable GlobalApp component creates the common infrastructure including a global Cosmos DB account, Traffic Manager, etc. A custom Pulumi component Global App 26 A factory function creates the infrastructure for a specific use case: both global and regional resources.
27. A reusable GlobalApp component creates the common infrastructure including a global Cosmos DB account, Traffic Manager, etc. A custom Pulumi component Global App 27 A factory function creates the infrastructure for a specific use case: both global and regional resources.
28. Global Function App 28
29. Azure Container Registry and a Docker Image are defined in the global scope. Global Container Instances App 29 A factory function creates an Azure Container Instances Group per region
30. Azure Container Registry and a Docker Image are defined in the global scope. Global Container Instances App 30 A factory function creates an Azure Container Instances Group per region
31. The infrastructure setup may be quite involved… Global VM Scale Sets App 31 And yet, the Global App component brings structure, simplifies the implementation, and helps avoid mistakes.
32. Evolve over Time Benefits of the abstraction
33. Example #1 v1 33 Multi-master support
34. Example #2 v1 34 Replace Azure Traffic Manager with Azure Front Door
35. Wrapping Up Final Thoughts
36. Cosmos DB and Pulumi 36 Azure Cosmos DB https://azure.microsoft.com/services/cosmos-db/ Pulumi https://www.pulumi.com/ Globally Distributed close to the users Azure Cosmos DB takes care of distributing the data and low-latency access. Pulumi simplifies the deployment of the compute infrastructure to match the best practices and the target tech stack. Infrastructure as Code Typescript / Python / Go Use the power of programming languages: general-purpose functions, conditions, loops, collection manipulation, compile-time errors, automated testing, refactoring, static analysis, linting. The tools you know and love. Abstractions reusable components Codify the best practices and distribute the implementation among the teams. Both components and applications can evolve over time.
37. • Globally-distributed Serverless Application in 100 Lines of Code. Infrastructure Included! https://www.pulumi.com/blog/globally-distributed-serverless-application-in-100-lines-of-code- infrastructure-included/ • Global App component example https://github.com/mikhailshilkov/pulumi-cosmos/ • Getting Started with Pulumi and Azure https://www.pulumi.com/azure/ Useful Links 37