skills.rest
fakhriaditiarahman
fakhriaditiarahmanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

backend-architect

Design scalable backend systems and APIs using microservices and event-driven patterns.

1|Updated Jan 20, 2026
Search Tags:#architecture#api design#backend#microservices#resilience#observability#event-driven
One-click install
npx skills add https://github.com/fakhriaditiarahman/Your-Skill-Agent --skill backend-architect-fakhriaditiarahman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-architect
Source: https://github.com/fakhriaditiarahman/Your-Skill-Agent/tree/main/.agent/skills/backend-architect
Command: npx skills add https://github.com/fakhriaditiarahman/Your-Skill-Agent --skill backend-architect-fakhriaditiarahman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides expert guidance for designing robust, scalable, and maintainable backend systems and APIs, ensuring they are performant and resilient from the outset.

Core Features & Use Cases

  • API Design: Specializes in REST, GraphQL, and gRPC, including versioning and contract definition.
  • Microservices & EDA: Architects microservice boundaries and event-driven systems using patterns like Saga and CQRS.
  • Resilience & Observability: Implements patterns like circuit breakers, retries, and comprehensive logging, metrics, and tracing.
  • Use Case: When starting a new microservice for user authentication, this Skill can define the API contract, communication protocols, security measures, and observability strategy.

Quick Start

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 a scalable microservice architecture for a new system?▼

Design scalable microservices by defining clear service boundaries, establishing inter-service communication protocols, and implementing resilient API contracts from the outset.

What is the best way to handle inter-service communication in event-driven architectures?▼

Event-driven architectures handle inter-service communication using patterns like Saga and CQRS to maintain data consistency and decouple services across distributed systems.

How do I make backend APIs more resilient against failures?▼

Make backend APIs resilient by implementing circuit breakers and retry patterns to prevent cascading failures and ensure system stability during partial outages.

What's the difference between REST, GraphQL, and gRPC for API design?▼

API design choices between REST, GraphQL, and gRPC depend on your specific requirements for contract definition, versioning, and the communication protocols your distributed system needs.

Do I need observability patterns like tracing and metrics for microservices?▼

Observability patterns including comprehensive logging, metrics, and tracing are essential for microservices to monitor distributed systems, track events, and diagnose performance issues.

When should I not use event-driven architecture for backend systems?▼

Event-driven architecture may be unnecessary for simple backend systems where synchronous API design suffices, as EDA introduces complexity through event patterns and eventual consistency.

Related Skills

Explore More Software Engineering Skills→
shafibabarshafibabar
1

bounded-context-mapping

Identify and document Bounded Contexts using Linguistic Fracture Line analysis.

Community
Advanced
camoneartcamoneart
5

microservices-patterns

Design microservice boundaries, contracts, and inter-service communication patterns for distributed systems.

Community
Advanced
mislam-devmislam-dev
1

microservices-architecture

Design microservices architectures with service boundaries and communication patterns.

Community
Advanced
MikisbellMikisbell

architecture-patterns

Generate layered and domain-driven backend architecture patterns with code samples.

Community
Intermediate