Case Study: Scaling Respond CMS
Taking Respond to the Cloud
Respond first took form in June 2012. The core idea for the product was to make it easy for site owners to build responsive web sites. It was one of the first content management systems that built responsive sites and was itself built with responsive web technologies. Since then, web applications transformed into single page applications (SPAs) and web sites have focused on fast, mobile experiences. As such, Respond has evolved by adopting flat file, static websites, Bootstrap 4, and the latest version of Angular.
To the Cloud
The next big leap for websites is moving toward a serverless, cloud infrastructure. This infrastructure makes sites more resilient, gives them the ability to scale to millions of users, and it just makes them run faster. Respond is once again ahead of the pack by offering the ability to store your resources (images, videos, etc.) in the Amazon cloud and even sync your entire site to the cloud.
Once your site is synced to the cloud, you can make use of Amazon's robust infrastructure to run your whole website. The best way to do this is to use Route 53 for DNS, Amazon Cloudfront for SSL/CDN, and Amazon S3 to store and version your files. Respond can then be used as a creative and staging environment for your site.
What's Next for Respond CMS
Now that Respond has completed its transition to a cloud oriented CMS, the next big step is to take all the common functions that the site uses to interact with Respond (for example: payment and form processing) and move those to Amazon Lambda functions. This will allow your site to run completely independent of the CMS and give you a truly autonomous setup. Look for this to come to Respond CMS in late 2018.