Overview

This section details the deployment options for Unique, offers guidance on infrastructure prerequisites, provides installation instructions tailored to the selected deployment model, and explains the upgrade process for new releases. Additionally, it includes release notes to keep clients informed about the latest platform developments.

High Level Deployment Overview

The following visualisation shows on a high level all Deployment models of Unique. While many abominations exist, the four most commonly used patterns are linked below.

Deploying Unique can be achieved through the four key models described earlier. However, all of them essentially involve coordinating across four primary layers:

1. Landscape: This layer encompasses the foundational elements such as infrastructure, identity management, governance, audit logging, and conditional access. It’s crucial to determine who is responsible for providing and managing these foundational components.

2. Infrastructure (or Resources): This layer includes the actual infrastructure, such as virtual machines, database servers, and other essential resources. Responsibility lies with the party providing and maintaining these elements.

3. Workload (Configurations): This layer involves the workloads or configurations required to ensure Unique operates effectively. It’s important to identify who is accountable for setting up and maintaining these configurations.

4. Unique (the Product): Unique itself is always provided by Unique. The only exception is when clients use the Software Development Kit (SDK) to extend Unique with their own custom logic.

For all these layers, it’s not just about determining who sets them up initially but also about identifying who will maintain them over the long term.

More clear responsibilities must be defined in the more elaborate models and you can find more information in the linked sections.

R: Responsible, A: Accountable, C: Consulted (billed by effort), I: Informed