The ArcGIS system patterns are abstractions of geospatial systems commonly implemented with ArcGIS software and services. They are not systems themselves and should not be deployed and used as is.
To reinforce this point, let us consider a different type of pattern: a sewing pattern for pants. In designing a pair of pants, you might start with a proven or popular pattern. You probably then pick out a fabric, and scale it to the target size. Using the pattern, you then tailor the pants to target user, and adjust some of the finer design elements like pockets, closures, and belt loops. In the end the pants you’ve designed bear little resemblance to the original pattern, though a trained eye might recognize that one was derived from the other.
ArcGIS system patterns are similar. Instead of fabric you’re choosing infrastructure. Instead of tailoring the legs to fit a person, you’re tailoring the system to fit the business and IT needs. There are many choices to make in designing systems based on system patterns, much as there are when designing pants from sewing patterns. Some decisions you may expect to make in designing your system include (but are not limited to):
For more on the system and solution architecture process see architecture practices of the ArcGIS Well-Architected Framework.
In many cases a single system pattern can be used as the basis for a system. This is true for the data editing and management system examples shown earlier, as well as most examples presented in the system pattern overview pages. But there are also cases where the needs of a system cannot be met by one system pattern alone; the capabilities from multiple system patterns are required.
As we begin to explore this concept, let us consider the three primary approaches to realizing systems from system patterns:
The system integration and system composition approaches are used when the capabilities of multiple system patterns are required. The decision to implement and integrate two systems or implement a single, composite system may involve many factors, including, but not limited to, reuse of capabilities across the enterprise, deployment, infrastructure, and physical architecture considerations, as well as IT governance practices within the organization.
Related resources:
Once you’ve identified one or more system and deployment patterns of interest, consider the following resources to learn more: