How isparxinfotech/datakawach works
Project type and purpose
• This is a single-page application (SPA) built with Angular (angular.json, src/app, tsconfig files).
• It provides user‐account management and file‐upload functionality to multiple cloud providers (S3, GCP, OneDrive), plus chat, metrics, and administrative dashboards.
File structure
• Top-level config: angular.json, tsconfig*.json, tailwind.config.js, package.json.
• Core UI layer: src/app/core/components (home, navbar, footer, account sub-components).
• Feature modules: account module houses login/register, dashboards, chat, upload flows.
• Services layer: src/app/services includes AuthService, ChatService, S3Service, GCPService, OneDriveService, AlertService, MetricsService, SuperAdminService.
• Environments: src/environments hold per-environment API endpoints and feature flags.
README
• (Empty aside from project name). Rely instead on file tree to infer external dependencies: AWS S3, GCP, OneDrive, plus an external authentication/REST API.
Main components and interactions
a. Frontend SPA
• Angular Components & Modules (UI layer)
• Angular Router (app-routing.module.ts)
• Shared UI (navbar, footer, alert)
b. Services Layer
• AuthService + AuthGuard → handles login flow, scoped to routes
• ChatService → WebSocket or REST chat API
• Cloud Storage Services (S3Service, GCPService, OneDriveService) → direct client‐SDK calls or proxied via API
• SuperAdminService + MetricsService → administrative endpoints
• AlertService → global notification bus
c. External Services
• Authentication Server (REST endpoints for login, register, personal info, session)
• AWS S3 buckets
• Google Cloud Storage buckets / Google Drive API
• Microsoft OneDrive API
• Chat backend (e.g. WebSocket or REST)
• Metrics/analytics backend
d. Data stores
• External databases and object stores (cloud providers)
Architectural patterns and design principles
• Component-driven UI (separate modules for account, navbar, footer).
• Dependency injection for services.
• Route-guarded navigation (AuthGuard).
• Service-oriented integration: each external integration has its own service.
• Model–view–service separation: models describe data; services handle data access; components handle presentation.