Understanding Instances in Vidos

An instance represents a specific configuration of a Vidos service within a region, serving an application’s distinct needs.

What are instances?

Each instance operates independently with its own configuration. Multiple instances of the same service can coexist, each optimized for different applications.

graph TD
    subgraph "Authorizer Service"
        A1[Instance 1: Mdl]
        A2[Instance 2: Payments]
    end

    UC1[Identity Verification] --> A1
    UC2[Authentication] --> A1
    UC3[Financial Transactions] --> A2

Different use cases leverage specialized instances. Identity verification uses the Mdl instance, while financial transactions use the Payments instance.

Regional context

Instances exist within regions:

• Each instance belongs to a specific region
• Instance scope is regional
• Management occurs within the region
• Data and processing remain within regional boundaries

Instance management

Each instance-capable service in Vidos has a corresponding management service within the same region. This management relationship reflects three key aspects:

• Creation and removal of instances
• Configuration of instance behavior
• Management of instance status

Instance-capable services

In Vidos, four core services support instances:

• Authorizer instances handle different authentication mechanisms
• Resolver instances manage identifier and address resolution
• Verifier instances perform different types of verification
• Validator instances apply varying validation rules

Each of these services can exist as multiple instances within a region, with each instance tailored to specific application requirements.

Configuration and state

Every instance maintains:

1. Configuration: The settings that define its behavior for a specific application
2. State: The information needed for operation

These aspects are managed regionally, ensuring that each instance maintains its intended purpose while operating within regional boundaries.