Deployment models


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 above.

Deploying Unique can be done over the four key models outlined above. But all of them basically involve ~4 layers that must be coordinated.

  1. Landscape - who provides the underlying foundations for infrastructure, identities, their governance and audit logging, conditional access etc.

  2. Infrastructure (sometimes called resources) - who provides the infrastructure itself, virtual machines, database servers and the sorts.

  3. Workload (Configurations) - who provides the necessary workloads or their configurations that are needed to run Unique successfully.

  4. Unique, the product itself - it is always Unique who provides that A small exception to this is the where clients can extend Unique for their logic.


For all these layers it's not only relevant who sets them up initially but also who maintains them on the long run.

High-level responsibilities

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

Layer / Tenant

PaaS

single tenant

customer-managed tenant

on-premise or 1-machine

Layer / Tenant

PaaS

single tenant

customer-managed tenant

on-premise or 1-machine

Product

RAC: Unique

I: Clients

[a collection of container images, amd64]

RAC: Unique

I: Clients

Workloads

[helm in the form of helmfiles]

Workload configurations

RAC: Unique

I: Clients

[helm in the form of helmfiles]

Workload configurations

RACI: to be defined

[helm in the form of helmfiles]

Workload configurations

RACI: to be defined

Infrastructure

[terraform or bicep]

Unique provisions all necessary infrastructure to run the workloads ahead. Unique maintains and pays the infrastructure up front.

 

RAC: Unique

I: Clients

[choice of customer, bicep]

By agreement with the customer either Unique (charged by effort) or the customer provisions and maintains the infrastructure.

The infrastructure is directly paid by the customer.

RACI: to be defined

[unclear, choice by customer]

The customer provisions and maintains the “infrastructure”.

Unique can advise or provision the infrastructure (charged separately by effort) but cannot maintain it as it is by definition out of reach.

 

Landscape

Unique operates the Azure AD tenant, implements policies and processes on it, manages users and roles and guarantees its security.

RAC: Unique

I: Clients

The customer operates the tenant, implements policies and processes on it, manages users and roles and guarantees its security.

The customer provides a runtime or orchestrator. The on-premise landscape is fully operated, governed and controlled by the customer and Unique will only advise (charged by effort)

Details

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

[remarks in the square brackets] are technology choices. You can learn more about them in .


Author

@Dominik Meyer

 

© 2024 Unique AG. All rights reserved. Privacy PolicyTerms of Service