skills.rest
ThanhNguyenDat
ThanhNguyenDatCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

backend-architect

Design scalable backend systems and APIs with service boundaries and communication patterns.

Updated Apr 26, 2026
Search Tags:#architecture#backend#microservices#resilience#distributed-systems#api-design
One-click install
npx skills add https://github.com/ThanhNguyenDat/agent-skills --skill backend-architect-thanhnguyendat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-architect
Source: https://github.com/ThanhNguyenDat/agent-skills/tree/main/backend-architect
Command: npx skills add https://github.com/ThanhNguyenDat/agent-skills --skill backend-architect-thanhnguyendat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the complexity of designing robust backend systems by providing a structured framework for service decomposition, API contract definition, and resilience planning.

Core Features & Use Cases

  • Architectural Design: Expert guidance on microservices, event-driven patterns, and service boundaries.
  • API Strategy: Comprehensive support for REST, GraphQL, and gRPC design, including versioning and documentation.
  • Use Case: When building a new multi-tenant SaaS platform, use this skill to define service boundaries, choose appropriate communication patterns, and plan for observability and fault tolerance from the start.

Quick Start

Use the backend-architect skill to design a microservices architecture for a new 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 service boundaries for a microservices architecture?▼

To design microservices service boundaries, you define structured service decomposition frameworks and inter-service communication patterns, ensuring distributed system scalability and maintainability for complex multi-tenant platforms.

What is the best way to plan fault tolerance for distributed systems?▼

Planning fault tolerance for distributed systems involves establishing resilience patterns and inter-service communication strategies that ensure robust operation and adherence to modern security best practices during backend failures.

How do I choose communication patterns for event-driven backend systems?▼

Choosing communication patterns for event-driven backend systems requires evaluating architectural guidance on service boundaries and communication strategies to ensure scalable and resilient inter-service data flow.

Can I use this approach to design REST, GraphQL, and gRPC APIs?▼

Yes, you can design REST, GraphQL, and gRPC APIs using comprehensive API strategy support that includes defining API contracts, versioning standards, and documentation for modern backend systems.

When do I need to define observability strategies for backend APIs?▼

You need to define observability strategies for backend APIs when building distributed environments like multi-tenant SaaS platforms, ensuring fault tolerance and maintainability from the architectural start.

Related Skills

Explore More Software Engineering Skills→
TonyQ-AITonyQ-AI
9

domain-modeling

Extract core business concepts, entity relationships, and domain rules from requirement specifications.

Community
Intermediate
ammonsdammonsd

aws-deployment

Automate AWS ECS infrastructure deployment with CloudFormation templates.

Community
Advanced
duylinhdang1998duylinhdang1998

microservices

Design microservices architectures with Eureka, Hystrix, Zuul, and deployment strategies.

Community
Advanced
engineers-hub-ltd-in-house-projectengineers-hub-ltd-in-house-project

idempotency

Implement idempotency key management for API requests and background jobs.

Official
Advanced