Infrastructure
고지 사항: 이 백서는 영어 버전이 공식 문서입니다. 다른 언어 버전은 참고용입니다。
System Architecture
섹션 제목: “System Architecture”┌─────────────────────────────────────────────────────────────────┐│ PIPO INFRASTRUCTURE │├─────────────────────────────────────────────────────────────────┤│ ││ ┌─────────────────────────────────────────────────────────┐ ││ │ FRONTEND │ ││ │ ├── Web App (React/Next.js) │ ││ │ ├── CDN (Cloudflare) │ ││ │ └── IPFS (backup hosting) │ ││ └─────────────────────────────────────────────────────────┘ ││ │ ││ ▼ ││ ┌─────────────────────────────────────────────────────────┐ ││ │ BACKEND │ ││ │ ├── API (Node.js/Express) │ ││ │ ├── Database (PostgreSQL) │ ││ │ ├── Cache (Redis) │ ││ │ └── Queue (Bull) │ ││ └─────────────────────────────────────────────────────────┘ ││ │ ││ ▼ ││ ┌─────────────────────────────────────────────────────────┐ ││ │ BLOCKCHAIN │ ││ │ ├── BSC (Primary) │ ││ │ ├── Base (Secondary) │ ││ │ ├── RPC Nodes (Alchemy/QuickNode) │ ││ │ └── Indexer (The Graph) │ ││ └─────────────────────────────────────────────────────────┘ ││ │└─────────────────────────────────────────────────────────────────┘Service Components
섹션 제목: “Service Components”Frontend
섹션 제목: “Frontend”| Component | Technology | Purpose |
|---|---|---|
| Web App | Next.js 14 | User interface |
| Wallet Connect | WalletConnect v2 | Wallet integration |
| CDN | Cloudflare | Global delivery |
| Hosting | Vercel + IPFS | Redundancy |
Backend
섹션 제목: “Backend”| Component | Technology | Purpose |
|---|---|---|
| API Server | Node.js/Express | Business logic |
| Database | PostgreSQL | User data, analytics |
| Cache | Redis | Performance |
| Queue | Bull/Redis | Async processing |
| Monitoring | DataDog | Observability |
Blockchain
섹션 제목: “Blockchain”| Component | Technology | Purpose |
|---|---|---|
| Primary Chain | BSC | Main deployment |
| Secondary Chain | Base | Alternative |
| RPC | Alchemy/QuickNode | Reliable access |
| Indexer | The Graph | Historical queries |
Reliability
섹션 제목: “Reliability”SLA Targets
섹션 제목: “SLA Targets”| Service | Uptime Target | Actual (est.) |
|---|---|---|
| Web App | 99.9% | TBD |
| API | 99.9% | TBD |
| Smart Contracts | 99.99% | N/A (blockchain) |
| Oracle | 99.5% | TBD |
Redundancy
섹션 제목: “Redundancy”Redundancy Strategy:├── Multi-region deployment (AWS/GCP)├── Database replication (primary + read replicas)├── CDN edge caching├── IPFS backup for frontend├── Multiple RPC providers└── Disaster recovery planMonitoring
섹션 제목: “Monitoring”Dashboards
섹션 제목: “Dashboards”- Application: Response times, error rates
- Blockchain: Gas prices, transaction success
- Business: Volume, TVL, user metrics
- Security: Anomaly detection, access logs
Alerts
섹션 제목: “Alerts”| Category | Threshold | Response |
|---|---|---|
| API latency | >500ms | Investigate |
| Error rate | >1% | Page on-call |
| TVL change | >10% | Review |
| Oracle deviation | >20% | Circuit breaker |