High-Level Architecture Diagram
Summary: This document provides a high-level visual representation of the STRIDE system architecture. It illustrates the main components and their interactions, offering a bird's-eye view of the platform.
System Flowchart
The diagram below shows the flow of requests and data across STRIDE's core modules and integrations.
flowchart TD
subgraph UI
A[Sales Rep / Admin (Web App)]
end
subgraph API Layer
B[API Gateway]
C[Auth Service (Google SSO)]
D[Tagging Engine]
E[Content Ingestion Service]
F[Search Engine (ElasticSearch/Meilisearch)]
G[Smart Content Pack Builder]
H[Analytics & Reporting]
end
subgraph Data & Integrations
I[(PostgreSQL / MongoDB)]
J[(ElasticSearch / Meilisearch)]
K[(Notion API)]
L[(Google Drive API)]
M[(Public Data APIs)]
end
A -->|HTTPS| B
B --> C
B --> D
B --> E
B --> F
B --> G
B --> H
D --> I
E --> K
E --> L
E --> M
F --> J
G --> I
H --> I
H --> J
Component Descriptions
- Web App (UI): The main interface for sales reps and admins to search, tag, and manage content.
- API Gateway: Single entry point for all client requests, handling routing, authentication, and rate limiting.
- Auth Service (Google SSO): Manages user authentication and role-based access.
- Tagging Engine: Applies and enforces structured tags across all content.
- Content Ingestion Service: Syncs and imports content from Notion, Google Drive, and public APIs.
- Search Engine: Provides fast, contextual search and filtering.
- Smart Content Pack Builder: Compiles and exports personalized content packs (PDF, etc.).
- Analytics & Reporting: Tracks usage, search trends, and content effectiveness.
- PostgreSQL / MongoDB: Primary data stores for users, content, and tags.
- ElasticSearch / Meilisearch: Search index for fast, contextual queries.
- Notion API / Google Drive API / Public Data APIs: External sources for ingesting and enriching sales collateral.
For more granular details, see the Low-Level Module Descriptions.