Skip to main content

Architecture Diagrams

This page uses simple text diagrams so the architecture remains readable in Git and in the docs site without extra rendering plugins.

System overview

Users
|
+--> intt-portal (Angular web)
|
+--> intt-mobile (Flutter app)
|
v
Core and domain APIs
- authentication-service
- setting-service
- data-service
- ticket-service
- gsb-service
- ngoss-service
- nocgrid-service
- nocpro-service
- tmf-service
- vital-service
|
v
Shared infrastructure
- MariaDB
- Redis
- RabbitMQ
|
v
Async workers and external systems
- caution-report queue
- ctt queue
- gsb queue
- changedp vendor queues
- kci queue
- tass queue
- vital queue
- APIM / TMFORCE / NIG / vendor endpoints

Auth and login flow

Browser
-> intt-portal
-> OIDC / SSO redirect
-> callback in intt-portal
-> auth/login API call
-> mvp1-authentication-service
-> token exchange and user context lookup
-> portal stores app tokens and user profile
-> portal loads shell and feature modules

Web request flow

Example: a user opens a ticket-related page in the web portal.

Browser
-> intt-portal
-> CoreAPIService selects backend base URL
-> Authorization header added by interceptor
-> mvp3-ticket-service
-> MariaDB / Redis / supporting modules
-> JSON response
-> intt-portal renders list, detail, or dashboard state

Async queue flow

Example: GSB or vendor-command flow.

Portal or mobile
-> mvp3-gsb-service
-> RabbitMQ publish
- intt_gsb_queue
- intt_alu_queue
- intt_zte_queue
- intt_fiberhome_queue
- intt_huawei_queue
-> queue worker consumes message
- gsb-queue-service
- changedp-queue-service
-> external network or APIM integration
-> result persisted or logged
-> downstream status available to API and UI

Reading tip

Use these diagrams with: