| If I were to do this, I think I would start somewhere along the lines of: 1 - $5 linode/digital ocean machines at different locations (CA, TX, NJ, London, wherever you want the things) These machines would run probably Nginx serving static up static content. They'd get this data pushed to them over something like rsync/scp from a central place. It would answer for the same domains, with the same content at each location. 2 - DNS Route53 / GeoDNS / Round-Robin Servers in all those locations are cool, but we want to get users close to them. I think Route53 does GeoIP DNS - routing users to the geographically closer machine. 3 - $10/$20 Linode at a central location for build/deploy. I'd probably look at Drone.io as the thing to take gitrepos and then build the website. This could handle JAM stack stuff pretty easily. Once it has the artifacts created, you ship them off to the linodes in step one to be served. This is kind of the broad view of where I would start for technologies to help with that kind of thing. Then comes a lot of glue and programs to make it easier to use. The form submission stuff they made seems pretty cool. You could make something that scans the artifacts looking for forms with a given data attribute, and when you find them build a data model to match and stuff in a POST address. Making that would be really fun. I hope this helps, I also dig this kind of stuff =) |