How jmartin82/mmock works
Main Components
a) Core Server Components:
• Mock Server (Port 8083)
• Console Server (Port 8082)
• TLS Server (Port 8084)
b) Key Functional Modules:
• Config Management System
• Request Matcher
• Response Generator
• Proxy Handler
• Scenario Manager
• Statistics Collector
• WebSocket Real-time Updates
c) Storage Components:
• Mock Definitions Store
• Request History Store
• Scenario State Store
Component Relationships
Client Requests -> Mock Server
• > Request Matcher
• > Mock Definitions Store
• > Scenario Manager
• > Proxy Handler (if proxy mode)
• > Response Generator
• > Variable Processor
• > Request History Store
• > WebSocket Updates -> Console UI
Important Details
a) API Endpoints:
• /api/request/* (verification endpoints)
• /api/scenarios/* (scenario management)
• /api/mapping/* (mock definition management)
• /echo (WebSocket endpoint)
b) File Structure Integration:
• Config folder for mock definitions
• TLS configuration location
• UI component location
Architectural Patterns to Highlight
• REST API architecture for management
• Event-driven architecture for real-time updates
• Plugin-based architecture for variable processors
• State machine pattern for scenarios
Implementation Details
Following aspects:
• Mock definition formats (JSON/YAML)
• Variable interpolation system
• Request matching logic
• Scenario state transitions
• Proxy mode operation
External Integrations
Connections to:
• External services (for proxy mode)
• File system (for configuration)
• Callback endpoints
• WebHook destinations
Notes
Annotations for:
• Default ports (8082, 8083, 8084)
• Supported protocols (HTTP/HTTPS)
• Configuration hot-reload capability
• Real-time monitoring features
• Mock definition management
• Request matching and response generation
• Scenario management
• Verification capabilities
• Real-time monitoring
• Proxy functionality