Backend Service Patterns

What it does

This skill provides guidance on common backend service patterns. It helps identify appropriate architectural approaches for building scalable and maintainable systems, including considerations for microservices, event-driven architectures, and API design. The goal is to improve the quality of backend system designs by leveraging established best practices.

When to use it

• When designing a new backend service or application architecture.
• To evaluate existing backend systems and identify potential improvements.
• During code reviews to ensure adherence to recommended patterns.
• For troubleshooting performance bottlenecks in backend services.
• When exploring options for migrating monolithic applications to microservices.

Key capabilities

• Microservice pattern identification
• Event-driven architecture guidance
• API design recommendations
• Scalability considerations
• Maintainability best practices

Example prompts

• "What are the pros and cons of using a message queue in my backend?"
• "Suggest an architectural pattern for handling user authentication across multiple microservices."
• "How can I improve the API design for this endpoint: /users/{id}?"

Tips & gotchas

This skill assumes some familiarity with backend development concepts. It's most effective when used in conjunction with a specific problem or scenario, rather than as a general knowledge resource.