Skip to main content

container View

The container view zooms into an individual enterprise system to reveal its internal software decomposition into applications, microservices, internal components, and autonomous AI agents.


Visual Projection

container view visual diagramcontainer view visual diagram

Container View showing microservices, components, and AI agents inside a system boundary


Purpose & Target Audience

  • Target Audience: Solution Architects, Tech Leads, Software Engineers, DevOps Engineers.
  • Primary Use Cases:
    • Zooming into a single system boundary to understand internal modularity.
    • Modeling frontend web/mobile clients, REST APIs, and backend workers.
    • Documenting how autonomous agent entities interact with internal services.
    • Designing service-to-service communication paths and database access.

Supported Entity Types

Entity TypeContainer RoleDescription
systemBoundary FrameThe parent container enclosing all internal software assets.
appService / ApplicationMicroservice, web API, frontend SPA, or worker daemon.
componentGranular ModuleIn-process handler, library, filter, or protocol controller.
agentAI Agent / CopilotAutonomous cognitive agent, LLM supervisor, or automated worker.
data_objectDomain DataSchema entities and transactional data tables accessed by apps.
infrastructurePersistence TargetEmbedded databases or private queues backing the system.

Supported Relationships & Verbs

Relationship VerbSource EntityTarget EntityTypical Representation
composed_ofsystem, appapp, component, agentBoundary nesting & composition
depends_onapp, component, agentapp, component, agentInternal service dependency edge
reads, writesapp, component, agentdata_objectData access & persistence edge
protectsagent, control, componentapp, component, data_objectSecurity, authentication & telemetry monitoring edge
flows_toapp, componentapp, componentSynchronous / asynchronous data flow

Filtering & Layout Recommendations

  • Recommended Layout: auto_layout LeftToRight (ingress to egress pipeline) or auto_layout TopToBottom.
  • Common Predicates:
    • include sys_payment_gateway: Target an explicit system by ID.
    • include app where api_type == "REST": Highlight exposed REST services.
    • exclude where status == "Deprecated": Remove deprecated modules.

Complete DSL Example

views {
container v_payment_hub_internals "Payment Hub Internal Architecture" {
# Target the core system and its internal modules
include sys_payment_hub
include app
include component
include agent
include data_object

# Include internal interactions
include_verb depends_on
include_verb reads
include_verb writes
include_verb protects

# Horizontal flow layout
auto_layout LeftToRight

# Style AI agents prominently
style agent where autonomy_level == "High" {
css_class "agent-highlight"
icon "bot"
}
}
}