Week 20 • Day 1Week 20
Day 1:Microservice Production Architecture & Schemas
Battle-tested daily lesson note • 100% runnable code, interview Q&A, test suite & interactive quiz
Day 1: Microservice Production Architecture & Schemas
1. First-Principles: Enterprise Request Contracts
In production AI microservices, an endpoint must accept authenticated tenant requests, validate inputs with strict boundary constraints (min/max query lengths, allowed tags, token caps), and return deterministic JSON responses:
python
class CopilotQueryPayload(BaseModel):
api_key: str = Field(..., description="Authenticated tenant API key")
session_id: str = Field(..., min_length=3, description="Chat session identifier")
query: str = Field(..., min_length=3, max_length=2000, description="Incident query")
service: str = Field(default="core-api", description="Target service")
traceparent: Optional[str] = Field(default=None, description="W3C traceparent header")
All production code and tests for this architecture reside in:
capstones/month05_production_fastapi_mlops/src/production_copilot_microservice.py(available in Tab 2: Codes)capstones/month05_production_fastapi_mlops/tests/test_capstone_month05.py(available in Tab 4: Test & Troubleshooting)
In Simple English: Designing Clean Request/Response Contracts (Month 5 Capstone Step 1)
Before writing a single web route, Staff Engineers lock down exact input/output schemas:
- Input Validation: Reject empty queries, over-limit prompts (>8,000 chars), invalid
tenant_id, or bad model choices cleanly (HTTP 422) before touching a database or LLM. - Output Envelope: Guarantee every response includes
request_id,answer,citations,cache_hit,latency_ms, andestimated_cost_usdso web dashboards and mobile clients never break.
Try It Free in Your Browser: Check Tab 2 (Codes) & Tab 4 (Test & Troubleshooting) to run our pure-Python Capstone Schema & Contract Validator right in Pyodide!