Service Architecture
Understanding a complex system begins with seeing its structure. The Service Architecture View in Sequa provides an interactive, high-level map of your software ecosystem, allowing you to visualize your services and the relationships between them.
This view is more than just a static diagram; it’s your primary navigational tool for exploring the documentation. Each node on the graph represents a service and acts as a direct gateway to its specific documentation within Live Docs.
Key Features
- Visual Exploration: The architecture view renders your services as nodes on a canvas, with lines indicating dependencies and relationships. This gives you an immediate, intuitive understanding of how your system is put together.
- Interactive Canvas: You can pan, zoom, and rearrange the nodes on the canvas to focus on specific areas of your architecture. Clicking on any service node will take you directly to the Live Docs Overview for that particular service.
- Centralized Navigation: Instead of navigating through complex folder structures or long lists, the architecture view provides a simple, visual way to find the service you’re looking for and dive into its documentation.
The Blueprint for Indexing
The Service Architecture View is not just a read-only visualization; it is a critical control interface that defines the scope of Sequa’s knowledge. The services you define on this map act as the blueprint for the indexing process.
- Define Your System: You can add, remove, and configure service nodes to create an accurate representation of your system’s components.
- Control the Scope: Only the services that exist as nodes on this architecture map will be indexed and analyzed by Sequa. If a service isn’t on the map, it remains invisible to the system.
By giving you direct control over how your architecture is defined, Sequa ensures that the generated documentation and analysis are always focused on the components that matter to you.
Next: Learn how to populate your Live Docs with content by creating your first page: Create self-maintaining pages.