Systems in ArchTechLytics

In ArchTechLytics, a System is a logical grouping of Azure resources that together deliver a capability — such as a customer portal, internal API, or mission-critical workload.

Systems allow you to evaluate architecture not at the individual resource level, but in the context of what that group of resources is meant to do.

Each System combines declared architectural intent (such as criticality, RPO, RTO) with actual cloud implementation (resources, configurations, security posture). This pairing enables powerful, context-aware analysis.

🧱 Why Systems?

Traditional cloud tools focus on resources and evaluates them in isolation.
ArchTechLytics focuses on purpose-driven architecture by:

Scoring systems based on their criticality
Analyzing completeness (e.g., is logging in place and backups present?)
Evaluating configurations in the context of your system’s purpose

This means systems are evaluated holistically — not just on what’s present, but also what’s missing.

For example:

A Virtual Machine without backup may be acceptable in a test system
But in a life-critical system, that same configuration would trigger a critical alert

🧠 What Does a System Include?

Each System includes:

Metadata
- Name, description, lifecycle stage (development, production, etc.)
- Contacts responsible for the system
Declared Intent
- System criticality (life-critical, mission-critical, etc.)
- RPO (Recovery Point Objective) and RTO (Recovery Time Objective)
- Optional: Threat model and methodology
Cloud Resources
- Mapped Azure resources (e.g., VMs, App Services, Key Vaults)
- Logging, monitoring, networking, storage, identity, and more

⚙️ How Systems Are Created

Systems can be created via the ArchTechLytics portal. Each System comprises:

System Basics — name, system contacts, description, lifecycle stage
Declared Intent — criticality, RPO, RTO, optional threat model and SLOs (future)
Cloud Resources — select Azure resources (e.g., VMs, Key Vaults, App Services) the system uses to deliver its purpose.

Once a System is created, it’s immediately processed by the scoring engine to generate scores, analytics, and recommendations.

Aspects of the System not exposed during creation (i.e. lifecycle stage) become manageable on the ArchTechManager page.

🔄 Continuous Evaluation

After creation, a System is continuously evaluated as changes occur:

Resource configuration changes (e.g., enabling backups)
Resources added or removed from the System
Updates to your declared System intent (e.g., changing criticality)

These changes trigger automatic re-scoring, ensuring your architecture stays aligned with best practices over time.

➡️ Learn more about:

⬆️ Back to top