backend-architect

Design scalable microservices architectures with API contracts and resilience patterns.

Updated Jan 9, 2025

Search Tags:#architecture #scalability #api design #backend #microservices #resilience #distributed systems

Ready to run

npx skills add https://github.com/baotoq/go-shortener --skill backend-architect-baotoq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backend-architect
Source: https://github.com/baotoq/go-shortener/tree/main/.agents/skills/backend-architect
Command: npx skills add https://github.com/baotoq/go-shortener --skill backend-architect-baotoq

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 meet complex functional and non-functional requirements from the outset.

Core Features & Use Cases

API Design: Masters REST, GraphQL, and gRPC, defining clear contracts and versioning strategies.
Microservices Architecture: Specializes in service boundary definition, inter-service communication, and distributed patterns like Sagas and CQRS.
Resilience & Observability: Integrates patterns like circuit breakers, retries, logging, and distributed tracing.
Use Case: Design a microservices architecture for a new e-commerce platform, including API contracts, communication protocols, and resilience strategies for order processing.

Quick Start

Design a scalable microservices architecture for a new e-commerce platform, focusing on order processing and inventory management.

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 an e-commerce platform?▼

Designing scalable microservices architecture involves defining clear service boundaries, establishing inter-service communication protocols, and implementing distributed patterns like Sagas and CQRS for resilient order processing and inventory management.

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

Defining service boundaries in distributed systems requires analyzing domain capabilities to isolate functionalities, ensuring maintainable APIs, and minimizing tight coupling to achieve scalable and resilient inter-service communication.

How do I choose between REST, GraphQL, and gRPC for API design?▼

Choosing between REST, GraphQL, and gRPC for API design depends on your client requirements, with the architecture defining clear contracts and versioning strategies to ensure robust and maintainable backend APIs.

How do you implement resilience patterns like circuit breakers in backend systems?▼

Implementing resilience patterns in backend systems involves integrating circuit breakers, retries, logging, and distributed tracing to handle failures gracefully and maintain observability across microservices architectures.

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

You need event-driven architecture when building scalable, resilient backend systems that require asynchronous inter-service communication, utilizing distributed patterns like CQRS to handle complex workflows and non-functional requirements.

Does this approach support system-wide non-functional requirements for high traffic applications?▼

Yes, this approach addresses system-wide non-functional requirements by designing scalable, resilient backend architectures that integrate observability, distributed patterns, and robust API contracts for high traffic applications.