In this chapter, we covered quite a few patterns to discuss how to handle data that is dynamic. In the clone server pattern, we demonstrated how to maintain data on a master instance, and clone it to slave instances. This allowed us to scale out and not miss any data. Next we moved to the NFS sharing pattern in which we used a single data store under NFS to hold the data. This allowed us to scale out without having any point-in-time issues with our data. We then moved to the state sharing pattern where we demonstrated the use of a key-value store, such as ElastiCache, and touched on some examples of how to add this into our infrastructure. We then moved to the URL rewriting pattern in which we demonstrated how we could move all of our static assets, such as images and JavaScript files, into S3 and rewrite them from the HTTP server, without any user disruption. Lastly we talked on the cache proxy pattern in which we optimized the user experience further by caching the static assets...