Geode pattern

The geode pattern should be used when your applications have users distributed over a wide area and you want to deliver a highly scalable solution. The geode pattern entails distributing a set of backend services over several geographical nodes, each of which can handle any request from any client in any location. When building scalable solutions, data scaling is as important as application scaling. Many companies consider scaling out their frontend apps and sharing a single instance of the data that's been deployed to a central remote location. As a canonical practice, data should be closer to where the application is deployed. The geode pattern improves latency and performance by distributing the traffic based on the shortest path to the closest geode, where each geode is behind the load balancer, such as Azure Front Door or Traffic Manager.

The key difference between the geode pattern and deployment stamps is that with deployment stamps, the data can be fragmented...