Marketpath CMS is a true software-as-a-service, decoupled, and optionally headless CMS comprised of three distinct parts:
Fig. 1 - Three components overview
These separate components increase the availability and performance of your sites while improving the overall security and lowering the risk of malicious visitors.
By default, live sites are published to a shared instance. Each instance is comprised of two or more load-balanced virtual machines and a database. Multiple sites may be published to each instance and balanced appropriately. If any site sees an increase in traffic we will automatically increase server capacities to handle the load and avoid impact on other sites sharing the instance. If a site sees high activity for a prolonged period of time, we will move it to an instance with more available capacity or to its own private instance.
For an additional monthly fee, any account can request a private, isolated instance. This allows a customer to host one or more sites, typically high traffic sites, on their own instance and adjust server capacities however necessary to handle the loads.
Fig. 2 - Multiple site instances
Marketpath uses multiple agents for various tasks. Three of these agents are shown in the images above. Here is a list of several agents used to process content and manage sites:
The Preview Site environment is an exact replica of the Live Site environment, with a couple small exceptions. If the site developer follows Marketpath's recommended best practices, editable content will be wrapped in additional <div></div> or <span></span> tags. This allows us to add a class to the tags and provide interactions between the preview pane and page edit pane. In most cases this will cause no change to styling unless the developer has specific parent>child styles in place (not a best practice anyway).
Marketpath CMS uses an API layer for all interactions between the Management UI and the underlying data. Every single action, change, lookup or other request that comes through the API is validated and authorized against real-time security settings.
Fig. 3 - API overview
While we utilize the API for all Management UI functions (and some external integrated tools), it is not yet available for standard users. We do expect to open this up in the future for custom integrations.
Marketpath CMS is hosted with Microsoft Azure and takes advantage of a large number of Azure service offerings.
Please fill out the form below with your feedback or any questions you may have after working through the "Application Architecture" lesson.