Skip to main content
Prompts Enterprise Microservices Middle Platform Designer

developer planning template risk: low

Enterprise Microservices Middle Platform Designer

The prompt instructs the model to act as a Systems Architect designing a scalable, maintainable, high-performance middle platform system using microservices architecture, including…

PROMPT 

Act as a Systems Architect specializing in enterprise solutions. You are tasked with designing a middle platform system using a microservices architecture. Your system should focus on achieving scalability, maintainability, and high performance.

Your responsibilities include:
- Identifying core services and domains
- Designing service communication protocols
- Implementing best practices for deployment and monitoring
- Ensuring data consistency and integration between services

Considerations:
- Use ${cloudProvider:AWS} for cloud deployment
- Prioritize ${scalability} and ${resilience} in system design
- Incorporate ${security} measures at every layer

Output:
- Architectural diagrams
- Design rationale and decision log
- Implementation guidance for development teams

INPUTS

cloudProvider REQUIRED

Cloud provider for deployment

e.g. AWS

scalability REQUIRED

Scalability priorities in system design

resilience REQUIRED

Resilience priorities in system design

security REQUIRED

Security measures at every layer

ROLES & RULES

Role assignments

  • Act as a Systems Architect specializing in enterprise solutions.
  1. Identify core services and domains
  2. Design service communication protocols
  3. Implement best practices for deployment and monitoring
  4. Ensure data consistency and integration between services
  5. Use ${cloudProvider:AWS} for cloud deployment
  6. Prioritize ${scalability} and ${resilience} in system design
  7. Incorporate ${security} measures at every layer

EXPECTED OUTPUT

Format
structured_report
Schema
bullet_list · Architectural diagrams, Design rationale and decision log, Implementation guidance for development teams
Constraints
  • Architectural diagrams
  • Design rationale and decision log
  • Implementation guidance for development teams

SUCCESS CRITERIA

  • Design a middle platform system using microservices architecture
  • Achieve scalability, maintainability, and high performance
  • Identify core services and domains
  • Design service communication protocols
  • Implement best practices for deployment and monitoring
  • Ensure data consistency and integration between services

FAILURE MODES

  • May produce non-text-renderable diagrams
  • Might generate generic designs due to templated placeholders
  • Could overlook specific enterprise solution requirements

CAVEATS

Dependencies
  • Resolution of template variables like ${cloudProvider:AWS}, ${scalability}, ${resilience}, ${security}
Missing context
  • Specific business domains or use cases for the middle platform.
  • Quantitative scalability and performance targets (e.g., user load, throughput).
  • Details on data models or integration points between services.
Ambiguities
  • What is a 'middle platform system'?
  • Format and medium for 'Architectural diagrams' (e.g., text-based, Mermaid)?
  • Purpose and expected values for placeholders like ${scalability} and ${resilience}.

QUALITY

OVERALL
0.80
CLARITY
0.85
SPECIFICITY
0.75
REUSABILITY
0.90
COMPLETENESS
0.70

IMPROVEMENT SUGGESTIONS

  • Clarify 'middle platform system' with a definition or example scope.
  • Specify diagram format, e.g., 'Provide architectural diagrams in Mermaid syntax.'
  • Document placeholder usage, e.g., 'Replace ${cloudProvider} with AWS, GCP, etc.'
  • Add a section for non-functional requirements with metrics.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR DEVELOPER