backend-architect

Design scalable backend systems with microservices and event-driven patterns.

Updated Dec 3, 2025
One-click install
npx skills add https://github.com/ankitsharma495/Flowbase --skill backend-architect-ankitsharma495
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-architect
Source: https://github.com/ankitsharma495/Flowbase/tree/main/.agents/skills/backend-architect
Command: npx skills add https://github.com/ankitsharma495/Flowbase --skill backend-architect-ankitsharma495

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity of designing robust, scalable, and maintainable backend systems and APIs, ensuring that new services are built on a solid architectural foundation.

Core Features & Use Cases

  • API Design: Masters REST, GraphQL, and gRPC, defining clear contracts and versioning strategies.
  • Microservices Architecture: Guides service boundary definition, inter-service communication, and resilience patterns.
  • Event-Driven Architectures: Designs systems leveraging message queues and event streams for asynchronous processing.
  • Use Case: When building a new e-commerce platform, this Skill can help define the microservices for order management, user authentication, and product catalog, ensuring they communicate effectively and scale independently.

Quick Start

Use the backend-architect skill to design a scalable microservices architecture for a new social media platform.

Frequently Asked Questions about backend-architect

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

FAQPage Schema
How do I design scalable microservices architecture for a new platform?▼

To design scalable microservices architecture, you must define clear service boundaries, establish inter-service communication protocols, and implement resilience patterns to ensure services operate and scale independently.

What is the best way to define service boundaries for distributed systems?▼

Defining service boundaries for distributed systems involves analyzing domain capabilities to isolate functionalities, ensuring maintainable services that communicate effectively through well-defined contracts and asynchronous event streams.

How does event-driven architecture work for asynchronous backend processing?▼

Event-driven architecture works by leveraging message queues and event streams to decouple services, enabling asynchronous processing where services react to events rather than waiting for synchronous responses.

Should I use REST, GraphQL, or gRPC for API design in microservices?▼

REST, GraphQL, and gRPC each serve API design differently: REST defines clear resource contracts, GraphQL offers flexible querying, and gRPC enables high-performance inter-service communication with strict versioning strategies.

How do I implement resilience patterns for backend services?▼

Implementing resilience patterns for backend services requires defining fallback mechanisms and retry logic within inter-service communication, ensuring distributed systems maintain availability during partial failures.

When do I need event-driven architectures for backend service development?▼

You need event-driven architectures for backend service development when building systems that require asynchronous processing, decoupled inter-service communication, and scalable handling of message queues and event streams.