{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":40762,"path":"platform-security/bp-sp-reference-arch-ds.md","title":"Service provider reference architecture","bundle":null,"doc_type":null,"release":"australia","body":"\n# Service provider reference architecture\n\nYour customers can access service provider \\(SP\\) services by using a portal that is designed for them to reach their domain-separated instance.\n\n## Basic attributes of service provider reference architecture\n\n-   You do not assign fulfillers to a domain. Instead, you share them across domains. This makes it harder to audit how many fulfillers you have per domain.\n-   You can share and leverage domain administration. This means that there is no overhead and you can optimize licenses.\n-   The number of users on the instance can change when you get a new customer. A new customer can result in tens or even hundreds of thousands of new users on the system. The number of total users is virtually unlimited in one shared environment.\n\n\\[Omitted image \"bp-sp-reference-architecture-ds.png\"\\] Alt text: SP reference architecture\n\nThe portal for SP services is dedicated or shared to the SP shared instance. Service providers use ServiceNow shared instances to manage their service delivery.\n\n## Reference hierarchy for domain-separated instances\n\n\\[Omitted image \"bp-ds-hierarchy-3.png\"\\] Alt text: Reference hierarchy\n\n\\[Omitted image \"bp-dedicated-ds-hybrid-siam.png\"\\] Alt text: SP dedicated DS hybrid SIam\n\n-   **[Service provider reference architecture decision trees](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/bp-ded-instance-decision-tree.md)**  \nYou can use decision trees and a comparison chart to determine if a new customer should be added to a shared instance or to their own dedicated instance.\n-   **[Service provider reference architecture for dedicated instances](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/bp-sp-reference-arch-dedicated.md)**  \nService provider \\(SP\\) customers can access SP services by using a portal to a dedicated instance. SPs use these dedicated instances to manage their service delivery.\n-   **[Service provider reference architecture for hybrid](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/bp-sp-reference-arch-hybrid.md)**  \nUse the hybrid service provider \\(SP\\) reference architecture for a customized solution. Your customers require a dedicated instance for a specific service. They can still use the shared SP instance for other services, but it requires integration of each instance.\n-   **[Service provider reference architecture for Service Integration Management \\(SIAM\\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/bp-sp-reference-arch-siam.md)**  \nThe Service Integration Management Service Integration and Management \\(SIAM\\) for service provider \\(SP\\) architecture integrates services for a unified customer experience.\n\n**Parent Topic:**[Domain separation recommended practices for service providers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/bp-domain-sep-recommended.md)\n\n**Related topics**  \n\n\n[Domain separation explained]()\n\n[Domain separation hierarchies]()\n\n[Context and domain separation]()\n\n[Segregating and securing data with domain separation]()\n\n[Alternatives to domain separation]()\n\n[Evaluating the need for domain separation]()\n\n[Benefits of domain separation]()\n\n[How a database query works with domain separation]()\n\n[Domain separation levels of support]()\n\n[Domain separation terms]()\n\n[Domain-separate a custom table]()\n\n[Customizing domain properties and themes]()\n\n[Managing domain separation for specific uses]()\n\n[Configuring domain separation with the domain picker]()\n\n[Domain separation performance considerations]()\n\n[Setting up domain hierarchies]()\n\n[Checking domain logs for errors and warnings]()\n\n[Importance of the Default domain]()\n\n[Contains queries and domain access]()\n\n[Domain paths query method]()\n\n[Slow queries and SQL debugging]()\n\n[Before Query business rules]()\n\n[Avoiding domain path in scripts]()\n\n[Domain assignments]()\n\n[Domain separation and the Customer Service Management \\(CSM\\) plugin]()\n\n"}}