backend-architect

Design scalable backend architectures and API strategies for distributed systems.

Updated May 5, 2026
One-click install
npx skills add https://github.com/Movchanets/Microservices_Learning --skill backend-architect-movchanets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-architect
Source: https://github.com/Movchanets/Microservices_Learning/tree/main/.agents/skills/backend-architect
Command: npx skills add https://github.com/Movchanets/Microservices_Learning --skill backend-architect-movchanets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design robust backend systems when a product needs clear service boundaries, reliable integrations, and architecture that can scale without becoming difficult to maintain.

Core Features & Use Cases

  • Service Decomposition: Split a domain into bounded contexts with clear responsibilities and ownership.
  • API and Integration Design: Plan REST, messaging, gateway, and BFF patterns for synchronous and asynchronous communication.
  • Resilience and Operations: Define retries, circuit breakers, timeouts, observability, authentication, and rollout strategies.
  • Use Case: A team building an enterprise marketplace can use this Skill to shape order, catalog, and identity services, choose event-driven communication, and document trade-offs before implementation.

Quick Start

Ask the backend-architect skill to design a microservices architecture for your system, including service boundaries, API contracts, communication patterns, resilience, observability, and deployment guidance.

Frequently Asked Questions about backend-architect

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

FAQPage Schema
How do I design a microservices architecture with clear service boundaries and API contracts?

Microservices architecture design decomposes domains into bounded contexts, defines API contracts, and plans communication patterns. This creates reliable integrations and clear service boundaries for distributed systems.

What is the best way to implement event-driven communication and CQRS in distributed systems?

Event-driven communication and CQRS in distributed systems separate read and write models using asynchronous messaging. This decouples services, improving scalability and fault tolerance for complex backend operations.

When do I need a BFF pattern or API gateway for backend architecture?

A BFF pattern or API gateway is needed when coordinating multiple microservices for different client interfaces. They handle routing, authentication workflows, and synchronous or asynchronous communication integration.

How do I plan fault tolerance, retries, and circuit breakers for resilient backend services?

Plan fault tolerance by configuring retries, timeouts, and circuit breakers within backend architecture. This resilience planning prevents cascading failures across distributed systems and maintains service availability.

How do I set up observability and monitoring for microservices?

Set up observability by defining monitoring strategies within resilience planning. This tracks distributed system health, inter-service communication, and fault tolerance metrics across microservices.