4 architectural models for ServiceNow implementation
< this article was shared by Kapil Jacob on LinkedIn, retaining it for self educate >
The most commonly used architectural models used to meet complex requirements are:
Deliberate customization – This is a very flexible model that uses baseline capabilities to extend out-of-the-box (OOTB) applications for complex business requirements.
Application extension – This model extends baseline capabilities to provide a new, scoped, application based on an OOTB application. This lets you maintain the app’s original purpose with development and configuration for each independent user group.
Domain separation – This model takes advantage of OOTB functionality on a single ServiceNow instance to enable data and process segregation appropriate for separate business lines and/or customers. A shared database is leveraged across these segments.
Multiple instances – This model involves multiple production instances of ServiceNow that are each purpose-built for a specific set of business needs.
Want to know more? Check the link below to know more on "how to tackle architectural implementation models".