skills.rest
HCMUTE-RTIC
HCMUTE-RTICOFFICIAL
Explore all skills by this author →
WebsiteGitHub

backend-architect

Design backend architectures for scalable APIs, microservices, and distributed systems.

Updated Feb 21, 2026
Search Tags:#architecture#api design#backend#microservices#distributed systems#event-driven
One-click install
npx skills add https://github.com/HCMUTE-RTIC/fit-hcmute --skill backend-architect-hcmute-rtic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-architect
Source: https://github.com/HCMUTE-RTIC/fit-hcmute/tree/main/.agent/skills/backend-architect
Command: npx skills add https://github.com/HCMUTE-RTIC/fit-hcmute --skill backend-architect-hcmute-rtic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides expert guidance for designing robust, scalable, and maintainable backend systems and APIs, addressing complex architectural challenges.

Core Features & Use Cases

  • API Design: Expertise in REST, GraphQL, and gRPC, including versioning and contract definition.
  • Microservices & EDA: Proficient in designing microservices architectures and event-driven systems.
  • Resilience & Observability: Implements patterns for fault tolerance and system monitoring.
  • Use Case: When starting a new backend service, consult this Skill to define its API contract, communication patterns with other services, and ensure it incorporates necessary resilience and observability features from the outset.

Quick Start

Use the backend-architect skill to design a RESTful API for a user authentication service.

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 microservices architecture for a new backend system?▼

To design scalable microservices, you must define clear service boundaries, establish inter-service communication protocols, and implement fault tolerance and observability patterns from the outset to ensure system maintainability.

What is the best way to define API contracts for distributed systems?▼

Defining API contracts involves selecting appropriate protocols like REST, GraphQL, or gRPC, and establishing strict versioning rules to ensure secure, performant, and reliable inter-service communication.

When do I need an event-driven architecture for my backend services?▼

You need an event-driven architecture when building distributed systems requiring asynchronous inter-service communication, loose service coupling, and high fault tolerance to handle complex, scalable backend workloads efficiently.

How do I implement resilience patterns for fault tolerance in distributed systems?▼

Implementing resilience patterns requires incorporating specific fault tolerance mechanisms into your backend architecture design, ensuring distributed services gracefully handle failures and maintain system availability during partial outages.

Does this approach support both RESTful API design and gRPC communication?▼

Yes, this architectural approach supports RESTful API design, GraphQL, and gRPC communication, providing expert guidance on contract definition, versioning, and selecting the optimal protocol for your specific backend service requirements.

Related Skills

Explore More Software Engineering Skills→
romiluz13romiluz13
161

requirements-analysis

Gather and analyze project requirements to define user stories and acceptance criteria.

Community
Basic
mahg-esmahg-es
3

cloud-deploy

Provision cloud infrastructure with Terraform, Pulumi, or CloudFormation.

Official
Advanced
masermediagroup-stackmasermediagroup-stack
1

using-message-queues

Coordinate asynchronous microservice communication using message queues and brokers.

Community
Advanced
jstzwjjstzwj
4

ray

Scale AI workflows across distributed systems with Ray.

Community
Intermediate