# eventtracing/dawn architecture

> Architecture diagram of the GitHub repository eventtracing/dawn, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-07-24). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/eventtracing/dawn
- Repository: https://github.com/eventtracing/dawn

## Overview

##### Project type and purpose
- This is a multi‐platform SDK suite and management platform (“曙光埋点 Dawn”) for full‐link event tracing.
- It provides lightweight client SDKs for iOS, Android and H5, plus a server‐side application (easyinsight-server) and a web portal (easyinsight-front) for event definition, validation, storage and analysis.

##### File structure
- At the root you have a container repo (this project) using Git submodules under `Sources/` for each sub‐project:
- `Android/EventTracing-Android`
- `iOS/EventTracing-iOS` plus debug & log‐viewer submodules
- `H5/EventTracing-web`
- `easyinsight/easyinsight-server`
- `easyinsight/easyinsight-front`
- No standalone `frontend`/`backend` directories at root; everything lives under `Sources/…`.
- Configuration files (.gitignore, .gitmodules, LICENSE, CODE_OF_CONDUCT) indicate a mono‐repo orchestrating several independent deliverables.

##### README for additional insights
- Names key features: auto instrumentation, VTree object model, link tracking.
- Lists deliverables: iOS SDK, Android SDK, H5 SDK, easyinsight-server, easyinsight-front.

##### Key elements to capture
- Git submodule “Sources/…” structure as the build/deployment starting point
- Each SDK’s internal layering: instrumentation → VTree → output channel
- easyinsight-server’s roles: schema management, ingestion API, storage adapter
- easyinsight-front’s roles: virtual tree editor, object management, real‐time validation dashboard
- Data flows: app user actions → SDK events → server → DB → UI

## Diagram (Mermaid)

```mermaid
flowchart TB
    subgraph "Client SDKs"
        IOS_SDK["iOS SDK\nInstrumentation→VTree→Output"]:::client
        IOS_DEBUG["iOS Debug Tools"]:::debug
        IOS_LOG["iOS Log Viewer"]:::debug
        AND_SDK["Android SDK"]:::client
        H5_SDK["H5 SDK"]:::client
    end

    subgraph "Backend"
        SERVER["easyinsight-server\nIngestion & Schema API"]:::backend
        DB["Database"]:::db
    end

    subgraph "Web UI"
        FRONT["easyinsight-front UI"]:::web
    end

    IOS_SDK -->|"Events (HTTP/native plugin)"| SERVER
    AND_SDK -->|"Events (HTTP/Gradle plugin)"| SERVER
    H5_SDK -->|"Events (HTTP/JS)"| SERVER

    IOS_DEBUG <-->|"Debug Channel"| IOS_SDK
    IOS_LOG <-->|"Log View"| IOS_SDK

    SERVER -->|"Write"| DB
    SERVER -->|"Read"| FRONT

    click IOS_SDK "https://github.com/eventtracing/dawn/tree/master/Sources/iOS/EventTracing-iOS"
    click IOS_DEBUG "https://github.com/eventtracing/dawn/tree/master/Sources/iOS/EventTracing-iOS-Debug"
    click IOS_LOG "https://github.com/eventtracing/dawn/tree/master/Sources/iOS/EventTracing-iOS-LogViewer"
    click AND_SDK "https://github.com/eventtracing/dawn/tree/master/Sources/Android/EventTracing-Android"
    click H5_SDK "https://github.com/eventtracing/dawn/tree/master/Sources/H5/EventTracing-web"
    click SERVER "https://github.com/eventtracing/dawn/tree/master/Sources/easyinsight/easyinsight-server"
    click FRONT "https://github.com/eventtracing/dawn/tree/master/Sources/easyinsight/easyinsight-front"

    classDef client fill:#B3DFFF,stroke:#0366D6,color:#000;
    classDef debug fill:#D6F5D6,stroke:#28A745,color:#000;
    classDef backend fill:#FFD8B1,stroke:#FF7F0F,color:#000;
    classDef db fill:#E0BBE4,stroke:#9C27B0,color:#000;
    classDef web fill:#B2DFDB,stroke:#00897B,color:#000
```
