VIRTEK · ARCHITECTURE LIBRARY

Architectures that give a project a real starting point

Not articles or marketing diagrams, but engineering patterns with boundaries, components, scale, recovery targets, controls, constraints and technology-stack options.

Find the closest target pattern22 baseline patterns · 24 service areas · fit validated in the lab

A reference is not a finished design

RTO/RPO and scale values are orientation points. They must not enter a specification until business criticality, dependencies, connectivity, licensing and operating procedures have been validated.

ENGINEERING CATALOGUE

Find the closest target pattern

Filters identify a useful starting point. The final design follows workload, data, integration and availability assessment.

22Found
Typical scale

From one department to a multi-tenant enterprise platform

On-premisesHybridCloud

Component set

SSO and rolesmodel gatewayingestion and indexvector databaseevaluationprompt audit

Constraints and boundaries

Quality depends on source content, access labels and an evaluation set; the model does not replace the process owner.

Security controls

Tenant isolation, ACL-aware retrieval, DLP, prompt protection, data masking, audit trails and human approval for critical actions.

Alternative technology options

Open-weight LLMs, vLLM/llama.cpp, PostgreSQL with pgvector and OpenSearch; sovereign models and platforms where required.

What to validate in the lab

Compare models, chunking, retrieval coverage, answer quality, context leakage and performance on a representative corpus.

Typical scale

From one workflow to an enterprise agent catalogue

On-premisesHybridCloud

Component set

agent cataloguetool registrypolicy enginetask queuetracingevaluationAgentOps

Constraints and boundaries

Autonomy is bounded by error impact; financial, HR and operational actions require approval gates.

Security controls

Short-lived authority, tool allowlists, secrets outside context, argument validation, decision audit and emergency stop.

Alternative technology options

Open orchestrators, MCP-compatible gateways, Kafka/RabbitMQ/NATS queues and local models to avoid single-cloud lock-in.

What to validate in the lab

Test tool failure, invalid arguments, human escalation, cost limits and result reproducibility.

Typical scale

From three nodes at one site to a dual-data-centre design

On-premisesHybrid

Component set

2+ load balancers3+ compute nodesdatabase clusterdistributed storagequorummonitoring

Constraints and boundaries

A cluster does not replace backup; inter-site latency and application behaviour determine the viable topology.

Security controls

Role segmentation, MFA for administration, encryption, hardening, bastion access and isolated management planes.

Alternative technology options

Proxmox VE, OpenStack or sovereign virtualisation; PostgreSQL/Patroni and alternative databases and storage where certified.

What to validate in the lab

Validate node, network, disk and site failure, quorum, split-brain, failover time, degraded operation and restore from backup.

Typical scale

From tens of VMs to multi-site estates and petabyte archives

On-premisesHybridCloud

Component set

backup serverdiverse repositoriesimmutable object/WORMcatalogueDR orchestrationrecovery testing

Constraints and boundaries

Copy count does not guarantee recovery: ownership, regular tests, dependency mapping and separate credentials are required.

Security controls

Immutability, air gap, separate management identity, MFA, dual control, deletion monitoring and malware scanning on recovery.

Alternative technology options

Veeam or compatible platforms, Bacula/UrBackup, S3 Object Lock, tape libraries and sovereign backup suites.

What to validate in the lab

Recover a complete service chain and validate RTO/RPO, immutability, clean backups, runbooks and operation without the primary identity domain.

Typical scale

From three to hundreds of branches, offices and remote users

HybridEdge / siteCloud

Component set

routersdual carriersSD-WANNGFWNAC/ZTNAIAM/MFADNS securityNMS/SIEM

Constraints and boundaries

Quality depends on local carriers, latency-sensitive applications and an accurate map of flows between segments.

Security controls

Continuous identity and posture checks, least privilege, microsegmentation, policy-based TLS inspection and central logging.

Alternative technology options

OpenWrt/VyOS/FRR, WireGuard/OpenVPN, sovereign NGFW/NAC and independent DNS and monitoring options.

What to validate in the lab

Emulate link loss, degradation, rerouting, compromised posture, IAM failure and access to critical applications.

Typical scale

From 3–6 nodes to multiple availability zones

On-premisesHybrid

Component set

self-service portalIAMvirtualisationKubernetesSDNSDSIaCchargebackmonitoring

Constraints and boundaries

Economics depend on utilisation, operating skills, licensing and image standardisation; small estates may not justify complex orchestration.

Security controls

Tenant separation, isolated management, MFA, secrets management, signed images, policy as code and continuous inventory.

Alternative technology options

OpenStack, Proxmox VE, Kubernetes, Ceph, OpenTofu/Ansible and sovereign cloud or virtualisation platforms.

What to validate in the lab

Validate node and storage failure, IaC deployment, scaling, quotas, tenant isolation and workload portability.

Typical scale

From 50 to several thousand concurrent sessions

On-premisesHybridCloud

Component set

gatewaysbrokervirtualisationGPU poolsprofilesfile servicesMFAMDM/EDRUX monitoring

Constraints and boundaries

Workload, peripherals, multimedia and latency must be measured; licensing and GPU can dominate cost.

Security controls

MFA, role-based data egress, clipboard and USB controls, segmentation, EDR and privileged session recording.

Alternative technology options

KVM/Proxmox, sovereign VDI and operating systems, Apache Guacamole for selected use cases and open profile services.

What to validate in the lab

Measure login and UX under loss, peripheral, GPU and printing compatibility, density and profile recovery.

Typical scale

From one department to a group-wide document registry

On-premisesHybridCloud

Component set

document cardsBPM/workflowfull-text searchsignaturedelegationEDINextcloud/S3ERPauditretention

Constraints and boundaries

Legal validity depends on signature type, document format, EDI operator and policy; a PDF is not a structured statutory document.

Security controls

Role and object access, immutable originals, signer MFA, certificate validation, malware scanning, legal hold and full audit.

Alternative technology options

Nextcloud, PostgreSQL/OpenSearch, sovereign DMS/EDI, approved signature providers and open BPM engines.

What to validate in the lab

Run a contract and statutory document end-to-end: versions, parallel approval, rejection, signing, receipts, search, archive package and recovery.

FROM PATTERN TO PROJECT

Capture inputs and validation criteria

Use a selected pattern as the foundation for a technical specification, RFP questionnaire, PoC or engineering assessment.