One-click install
npx skills add https://github.com/Kushal9889/claude-plugins --skill backend-architect-kushal9889
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-architect
Source: https://github.com/Kushal9889/claude-plugins/tree/main/architecture/skills/backend-architect
Command: npx skills add https://github.com/Kushal9889/claude-plugins --skill backend-architect-kushal9889

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the challenge of designing and implementing scalable, resilient, and maintainable backend systems and APIs, providing expert guidance for complex architectural decisions.

Core Features & Use Cases

  • Scalable API Design: Expertise in RESTful, GraphQL, gRPC, and WebSocket APIs.
  • Microservices Architecture: Specialization in service boundaries, communication, discovery, and API gateways.
  • Event-Driven Architecture: Proficiency in message queues, event streaming, and pub/sub patterns.
  • Security Patterns: Implementation of OAuth 2.0, JWT, RBAC, and ABAC for secure systems.
  • Resilience & Fault Tolerance: Techniques for circuit breakers, retries, timeouts, and graceful degradation.
  • Observability & Monitoring: Strategies for logging, metrics, tracing, and alerting.
  • Data Integration: Patterns for data access layers, ORM integration, and event-driven data sync.
  • Caching Strategies: Implementation of cache layers, patterns, and invalidation strategies.
  • Asynchronous Processing: Handling background jobs, task processing, and scheduled tasks.
  • Testing Strategies: Unit, integration, contract, and end-to-end testing approaches.
  • Deployment & Operations: Containerization, orchestration, CI/CD, and configuration management.
  • Documentation & Developer Experience: API documentation, architecture documentation, and developer portals.

Quick Start

Use the backend-architect skill to design a RESTful API for an e-commerce order management system.

Frequently Asked Questions about backend-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design microservices architecture for a scalable backend system?

Designing microservices architecture for scalable backend systems involves defining service boundaries, establishing inter-service communication, configuring service discovery, and routing requests through API gateways. This approach ensures decoupled components and resilient operations.

What is the best way to implement resilience and fault tolerance in backend APIs?

Implementing resilience and fault tolerance in backend APIs requires applying circuit breakers, configuring retries and timeouts, and executing graceful degradation strategies. These mechanisms prevent cascading failures and maintain system availability during partial outages.

When should I use event-driven architecture with message queues and pub/sub patterns?

Event-driven architecture using message queues and pub/sub patterns is needed for asynchronous processing and decoupled microservices communication. It enables systems to handle background jobs and event streaming efficiently without blocking primary operations.

Does this backend architecture guidance cover security patterns like OAuth 2.0 and JWT?

This backend architecture guidance covers security patterns including OAuth 2.0, JWT, RBAC, and ABAC. These protocols manage secure authentication and authorization, protecting APIs and microservices from unauthorized access.

How do I set up observability and monitoring for distributed microservices?

Setting up observability and monitoring for distributed microservices requires implementing centralized logging, collecting metrics, and configuring distributed tracing. These strategies provide actionable alerting and visibility into system health.

What caching strategies should I use for high-throughput data integration?

Caching strategies for high-throughput data integration involve implementing dedicated cache layers, applying appropriate cache patterns, and defining strict cache invalidation rules. This reduces database load and accelerates data access times.