|Direct Upload| B[Node.js Server]
B -->|Blocking Write| C[Local Filesystem /uploads]
B -->|In-Memory Map| D{RAM State}
style C fill:#f99,stroke:#333
style D fill:#f99,stroke:#333
end
subgraph "✅ v2.0 (Target Architecture)"
AA[User] -->|Stream| BB[Node.js Cluster]
BB -->|Async Stream| CC[S3 Object Storage]
BB -->|TTL Metadata| DD[Redis Cache]
style CC fill:#9f9,stroke:#333
style DD fill:#9f9,stroke:#333
end">
|Direct Upload| B[Node.js Server]
B -->|Blocking Write| C[Local Filesystem /uploads]
B -->|In-Memory Map| D{RAM State}
style C fill:#f99,stroke:#333
style D fill:#f99,stroke:#333
end
subgraph "✅ v2.0 (Target Architecture)"
AA[User] -->|Stream| BB[Node.js Cluster]
BB -->|Async Stream| CC[S3 Object Storage]
BB -->|TTL Metadata| DD[Redis Cache]
style CC fill:#9f9,stroke:#333
style DD fill:#9f9,stroke:#333
end">
|Direct Upload| B[Node.js Server]
B -->|Blocking Write| C[Local Filesystem /uploads]
B -->|In-Memory Map| D{RAM State}
style C fill:#f99,stroke:#333
style D fill:#f99,stroke:#333
end
subgraph "✅ v2.0 (Target Architecture)"
AA[User] -->|Stream| BB[Node.js Cluster]
BB -->|Async Stream| CC[S3 Object Storage]
BB -->|TTL Metadata| DD[Redis Cache]
style CC fill:#9f9,stroke:#333
style DD fill:#9f9,stroke:#333
end">
<aside>
🚨
CRITICAL SECURITY ASSESSMENT
The current "SecureShare" v1.0 relies on single-node, in-memory state and plaintext filesystem storage.
Risks:
- Data Loss: Server restart wipes all file metadata (Volatile RAM).
- Zero Privacy: Files are stored unencrypted in
uploads/.
- Denial of Service: Cleanup jobs (
fs.unlinkSync) block the main thread.
</aside>
graph TD
subgraph "⛔ v1.0 (Current Liability)"
A[User] -->|Direct Upload| B[Node.js Server]
B -->|Blocking Write| C[Local Filesystem /uploads]
B -->|In-Memory Map| D{RAM State}
style C fill:#f99,stroke:#333
style D fill:#f99,stroke:#333
end
subgraph "✅ v2.0 (Target Architecture)"
AA[User] -->|Stream| BB[Node.js Cluster]
BB -->|Async Stream| CC[S3 Object Storage]
BB -->|TTL Metadata| DD[Redis Cache]
style CC fill:#9f9,stroke:#333
style DD fill:#9f9,stroke:#333
end
| Feature |
⛔ v1.0 (Current) |
✅ v2.0 (Proposed) |
| Storage |
Local Disk (Plaintext) |
S3 / MinIO (Encrypted) |
| State |
In-Memory Map() |
Redis (Persistent) |
| Cleanup |
setInterval Loop (Blocking) |
Redis TTL (Automatic) |
| Scale |
Single Node |
Horizontal Cluster |
- Technical Implementation: Redis + S3 Middleware (Click to Expand)
- [ ] Phase 1: Provision Redis instance (ElastiCache or Docker).
- [ ] Phase 2: Update
upload.js to stream to S3 (Remove fs dependency).
- [ ] Phase 3: Deploy Load Balancer + 2 Node.js instances.