Back to Rules
Architecture
Claude Coder Microservices Communication Rules
Neura Market April 24, 2026
0 copies 0 downloads
System rules for designing inter-service communication in microservices architectures with DeepSeek Coder, covering sync/async patterns, error handling, and resilience.
Rule Content
# Claude Coder Microservices Communication Rules ## Communication Patterns ### Synchronous (REST/gRPC) - Use for: queries requiring immediate response, health checks, simple CRUD - Timeout: set explicit timeout for every outbound call (default: 5s, max: 30s) - Retries: max 3, with exponential backoff (1s, 2s, 4s) + jitter - Circuit breaker: open after 5 consecutive failures, half-open after 30s ### Asynchronous (Events/Messages) - Use for: commands that don't need immediate response, cross-service data sync - Message format: CloudEvents specification - Idempotency: every consumer must handle duplicate messages safely - Dead letter queue: configure for all consumers (max 3 retries before DLQ) - Ordering: only guarantee ordering within a partition key ## API Contract Rules 1. All APIs versioned (v1, v2) — never break backward compatibility 2. Use Protocol Buffers for gRPC, OpenAPI 3.1 for REST 3. Changes: additive only (new fields with defaults, new endpoints) 4. Breaking changes require: new version + migration period + deprecation notice 5. Consumer-driven contract testing with Pact or similar ## Data Consistency - Prefer eventual consistency — only use distributed transactions when legally required - Saga pattern for multi-service operations (choreography for simple, orchestration for complex) - Compensating transactions for rollback (undo the business action, not the DB transaction) - Outbox pattern for reliable event publishing (write event + business data in same DB transaction) ## Observability - Distributed trace ID propagated in ALL requests (X-Trace-Id header) - Structured logging with: trace_id, service_name, operation, duration_ms, status - Metrics per endpoint: request_count, latency_histogram, error_rate - SLOs defined per service: availability, latency p99, error budget
Comments
More Rules
View allContent
DeepSeek V3 Multilingual Content Generation Rules
System rules for generating content in multiple languages with DeepSeek V3, covering translation quality, cultural adaptation, locale-specific formatting, and quality assurance.
N
Neura MarketDevelopment
DeepSeek R1 Code Refactoring Safety Rules
System rules for safe code refactoring with DeepSeek R1, requiring test coverage verification, incremental changes, and behavior preservation checks.
N
Neura MarketDocumentation
DeepSeek V3 Technical Documentation Writer Rules
System rules for using DeepSeek V3 to generate clear, maintainable technical documentation including API docs, architecture docs, and onboarding guides.
N
Neura MarketDatabase
Claude Coder Database Query Optimization Rules
System rules for DeepSeek Coder to generate optimized database queries, with requirements for EXPLAIN analysis, indexing recommendations, and performance targets.
N
Neura MarketDevOps
DeepSeek V3 DevOps and Infrastructure Rules
System rules for using DeepSeek V3 to generate infrastructure code, CI/CD pipelines, and operational runbooks with security and reliability best practices.
N
Neura MarketWriting
DeepSeek R1 Academic Writing Assistant Rules
System rules for configuring DeepSeek R1 as an academic writing assistant that maintains scholarly tone, proper citations, and disciplinary conventions.
N
Neura Market