Design appropriate microservice boundaries
Help me define microservice boundaries for this system: Current system description: [DESCRIBE THE MONOLITH OR SYSTEM] Domain concepts: [LIST MAIN ENTITIES AND PROCESSES] Team structure: [HOW TEAMS ARE ORGANIZED] Scale requirements: [TRAFFIC, DATA VOLUME] Analyze and recommend: 1. Bounded contexts identification 2. Service boundary recommendations 3. Data ownership for each service 4. Synchronous vs async communication 5. Shared data handling strategy 6. Transaction boundary challenges 7. Migration sequence suggestion 8. Anti-patterns to avoid
Help me define microservice boundaries for this system: Current system description: [DESCRIBE THE MONOLITH OR SYSTEM] Domain concepts: [LIST MAIN ENTITIES AND PROCESSES] Team structure: [HOW TEAMS ARE ORGANIZED] Scale requirements: [TRAFFIC, DATA VOLUME] Analyze and recommend: 1. Bounded contexts identification 2. Service boundary recommendations 3. Data ownership for each service 4. Synchronous vs async communication 5. Shared data handling strategy 6. Transaction boundary challenges 7. Migration sequence suggestion 8. Anti-patterns to avoid
This prompt is released under CC0 (Public Domain). You are free to use it for any purpose without attribution.
Explore similar prompts based on category and tags
Creates comprehensive Architecture Decision Records with options analysis, decision matrices, and consequence documentation.
Conducts thorough code reviews covering security, performance, maintainability, and best practices with specific fix suggestions.
Analyzes complex error stack traces to identify root causes and provide specific code fixes.
Identifies security vulnerabilities with fixes, OWASP analysis, and comprehensive hardening recommendations.