How sammwyy/mikumikubeam works
Main Components Identification
a) Frontend Layer:
• Located in /src directory
• React-based UI with TypeScript
• Vite as the build tool
• Tailwind CSS for styling
b) Backend Layer:
• Located in /server directory
• Node.js server with TypeScript
• Worker-based architecture for attack handling
c) Data Layer:
• Located in /data directory
• Stores proxies and user agents
Architectural Pattern
a) Worker-based Architecture:
• Main server process
• Separate worker processes for different attack types:
• HTTP Flood Worker
• HTTP Slowloris Worker
• Minecraft Ping Worker
• TCP Flood Worker
b) Client-Server Communication:
• WebSocket or HTTP communication between frontend and backend
• Real-time attack statistics and control
Component Relationships
a) Frontend to Backend:
• Attack configuration requests
• Real-time status updates
• Proxy/UA management
b) Backend to Workers:
• Worker initialization
• Attack parameter passing
• Status reporting
c) Workers to Targets:
• Attack execution flows
• Proxy utilization
Flow Directions
• User interactions → Frontend
• Frontend ↔ Backend communication
• Backend → Worker initialization
• Workers → Target systems
• Data stores → Workers (proxy/UA usage)
Additional Elements
Include:
• System boundaries
• External interfaces (target systems)
• Network protocols used (HTTP, TCP, WebSocket)
Technical Details
Annotations for:
• Port numbers (3000 for server, 5173 for frontend)
• Worker thread management
• Attack method configurations
• Real-time data flow
Remember to include notes about the scalability aspects of the worker-based architecture and how it enables multiple attack types to run concurrently without impacting the main application's performance.
This system design should effectively communicate both the technical architecture and the user interaction flow while maintaining the project's unique characteristics as a network stress testing tool.