Layered System Architecture

Our solution is designed with a layered architecture, which is relevant when discussing updates, as each layer has its own update frequency and method. A diagram of these layers is provided below.  Integrations, connectors, and KeyShot Studio is not included for simplicity.

Open

Each layer has its own update scheme.

CONFIGURATION LAYER

Customers

Each customer has their own unique configuration, tailored to their specific needs. These configurations are updated through dialogue with individual customers. Service Delivery (SD) is the primary driver for managing and updating configurations.

Hub Configuration

The Hub uses a single configuration for all its users. This configuration is updated whenever new requirements are identified, impacting all Hub customers. The current configuration version is 1.1.

APPLICATION LAYER

The Core and Media Manager components handle the solution’s logic and user experience.

Feature Releases

New features are developed and released on a fixed cadence. These updates are deployed by SD through the platform portal, initially in the customer's TEST environment, and subsequently in PROD after validation by the customer. New features may require configuration adjustments to either enable them or align with legacy features.

Patch Releases

To address defects, security issues, and minor requests, patches are released on a monthly basis. These patches are deployed individually by SD for each customer and only exceptionally require configuration changes.

PLATFORM LAYER

The common hosting infrastructure is managed across two clusters: EU and North America (NA). This layer is developed and maintained by the Platform Team. Updates are deployed on a regular basis in pre-scheduled service window on Wednesdays after normal business hours, with announcements shared via Teams, including any expected downtime. 

Read platform policy here: https://digizuite.atlassian.net/wiki/spaces/RDG/pages/edit-v2/4045307905

MANAGED SERVCIES

A significant portion of the solution relies on managed services from Microsoft Azure, including MS SQL, Kubernetes, and others. Azure updates follows a predefined service window on the first Tuesday of each month, outside of normal business hours.