This blog post is part of the SaaS Headless Content Delivery Architectures Series (SHCDAS).
Static solutions are relatively simple to conceptualize, build, and administer. Separation of content and presentation from services can improve manageability. The entire site can be cached on a CDN, so solutions can perform very well, allowing low-cost scalability.
Dynamic content delivery extends static content delivery in that any application server can respond to an HTTPS request with a static file. In addition, dynamic content delivery allows logic while servicing each HTTP request rather than simply serving the contents of a file. URLs on the site may correspond to files that contain instructions to run on the server to generate unique output in response to each request. The main drawbacks of dynamic content delivery is the need to maintain application servers that can be difficult to scale.
With dynamic content delivery, developers typically edit application server code files, although it is possible for the build process to generate files that the application server interprets as code to execute. Rather than specifying paths or service URLs, URLs in dynamic solutions may correspond to data endpoints that run instructions such as processing files in locations completely unrelated to the path in the requested URL.
2 thoughts on “SHCDAS: CMS Deployment and Page Request Cycles”