Common usage patterns for Cloud CMS
Cloud CMS provides an API as well as an open-source Cloud CMS Application Server (using Node.js) that you can optionally use to provide middleware services for your front-end applications. Customers often take advantage of this to deliver web sites, custom APIs and CDN integrated content delivery.
Cloud CMS can be deployed in many topologies - some that incorporate middleware and others that do not. This page provides provides a breakdown of the most common architectures utilized in building out these applications.
Direct API Access
A browser or mobile client connects to the Cloud CMS API directly.
Custom Middle Tier
A browser or mobile client connects to a custom middle tier. The middle tier provides an externally facing API in service of those requestors and coordinates back-end connections to Cloud CMS and potentially other APIs as well.
Cloud CMS Application Server (embedded)
A browser or mobile client connects to a Node.js server running the
cloudcms-server module. This
module is Apache 2.0 licensed and provides caching, invalidation, CDN integration, page renditions and much
more. It helps customers to deliver powerful application servers where they have full authority to customize
it as they wish.
Cloud CMS Application Server (standalone)
A browser or mobile client connects to a Cloud CMS Application Server instance. Cloud CMS packages the Application Server into a standalone installation (using Docker typically) that makes sense for cases where customers have limited custom code and desire instead a more turnkey solution.