Microservices Architecture

knowledge skill

Decomposes a monolithic application into independent services based on bounded contexts. Produces a service map and API contract definitions for inter-service communication.

Worked examples

• {"input": {"monolith_spec": "E-commerce site with combined cart, payment, and inventory logic", "domain_entities": ["Order", "Product", "PaymentMethod", "Customer"], "scaling_requirements": "Inventory updates lag during high-traffic sales"}, "output": {"service_boundaries": ["OrderService: manages lifecycle of orders", "InventoryService: tracks stock levels", "PaymentService: handles gateway transactions"], "api_contracts": {"InventoryService": "/stock/{id} GET: returns quantity"}, "data_ownership": {"InventoryService": "products_stock_table", "OrderService": "orders_table"}}}
• {"input": {"monolith_spec": "Healthcare portal managing patient records, scheduling, and billing", "domain_entities": ["Patient", "Appointment", "Invoice", "Provider"], "scaling_requirements": "Billing reports slow down patient record access"}, "output": {"service_boundaries": ["PatientService: identity and records", "SchedulingService: calendar management", "BillingService: invoicing and payments"], "api_contracts": {"SchedulingService": "/book POST: creates appointment"}, "data_ownership": {"BillingService": "invoices_table", "PatientService": "patient_profiles_table"}}}

Input

• monolith_spec: string: description of current system functions
• domain_entities: array: list of core business objects
• scaling_requirements: string: specific bottlenecks to address

Output

• service_boundaries: array: list of defined microservices and their responsibilities
• api_contracts: object: mapping of service endpoints and data exchange formats
• data_ownership: object: mapping of database tables to specific services

Details

• Skill type: knowledge skill
• Safety level: safe_public_research
• Version: 1.0.0