How kumailr7/apiops-demo works
Client Layer
• External HTTP clients making API requests
• Supported endpoints (/fact, /facts, /add)
Ingress Layer
• ngrok Kubernetes Operator
• Traffic flow from internet to the service
• Gateway configuration (referenced in gateway.yaml)
Application Layer
• Go API Service Container
• Main service running in a Kubernetes pod
• Port (5000) the service listens on
Data Layer
• JSON file storage (facts.json)
• Ephemeral nature of the storage
• Internet/External Clients
• ↓
• ngrok Ingress Controller
• ↓
• Kubernetes Gateway
• ↓
• Go API Service Pod
• ↓
• JSON File Storage
Component Details
• For each API endpoint, show the HTTP method (GET/POST)
• Container specification (referenced from Dockerfile)
• Kubernetes deployment configuration
• Traffic policy rules
Additional Elements
• GET /fact
• GET /facts
• POST /add
• A note about the stateless nature of the application
• Container orchestration boundary
Technical Specifications to Note
• Go runtime environment
• HTTP server port (5000)
• JSON data format for requests/responses
• Kubernetes deployment specifications
Infrastructure Context
• Kubernetes cluster boundary
• Ngrok tunnel connection
• Ephemeral storage boundaries
Configuration file references (deployment.yaml, gateway.yaml, traffic-policy.yaml)
Remember to emphasize:
• The simplicity of the application
• The Kubernetes deployment aspect
• The ngrok integration for ingress
• The ephemeral nature of the data storage