Multi-sitemap vs Multi-instance

AgilityCMS provides several options when it comes to managing content for multiple websites. Normally, this means you have multiple instances each with its own database and users. However, it's worth exploring using multiple Sitemaps as well. Each has its pros and cons and it's important to understand the differences so you can choose the right solution for the right problem.

Multi-Instance

Multiple instances mean that you have one or many Instances.

• Separation of concerns
• Each website can have a vastly different or similar structure
• Maintain distinct lists of user access (i.e. User A should have had access to Instance B)
• Each instance has its own web application
• Limited or no dependencies on content from another instance - content can be retrieved from other instances by the web application via the REST API only
• Ability to "link" to other Instances to allow for copying of module and content definitions, pages, and shared content
• Dedicated database per instance
• Dedicated media and documents per instance

Multi-Sitemap

Multi-sitemap refers to having multiple Sitemaps within a single instance.

• Can map each Sitemap to a domain/subdomain
• Each have their own page tree
• Can have one web app per sitemap or a multi-tenant web application that powers all sitemaps
• All users that have access to the instance can access all content across sitepmaps - however permissions can be set to limit users to "read only" on sitemaps that are not relevant to the user
• All content is in a single database

Multi-Sitemap - One Web Application

Multi-Sitemap - Multiple Web Applications