This is my favorite take on this idea: https://www.colinsteele.org/post/27929539434/60000-growth-in-7-months-using-clojure-and-aws https://www.colinsteele.org/p

This is my favorite take on this idea: https://www.colinsteele.org/post/27929539434/60000-growth-in-7-months-using-clojure-and-aws https://www.colinsteele.org/post/27929539434/60000-growth-in... Quoting: "Because the data set is small, we can “bake in” the entire content database into a version of our software. Yep, you read that right. We build our software with an embedded instance of Solr and we take the normalized, cleansed, non-relational database of hotel inventory, and jam that in as well, when we package up the application for deployment. Egads, Colin! That’s wrong! Data is data and code is code! We earn several benefits from this unorthodox choice. First, we eliminate a significant point of failure - a mismatch between code and data. Any version of software is absolutely, positively known to work, even fetched off of disk years later, regardless of what godawful changes have been made to our content database in the meantime. Deployment and configuration management for differing environments becomes trivial. Second, we achieve horizontal shared-nothing scalabilty in our user-facing layer. That’s kinda huge. Really huge."