backend-architect

Provide phased architecture guidance for scalable backend systems across multiple languages.

9|1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/e-t-y-b/etyb-skills --skill backend-architect-e-t-y-b
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-architect
Source: https://github.com/e-t-y-b/etyb-skills/tree/main/skills/backend-architect
Command: npx skills add https://github.com/e-t-y-b/etyb-skills --skill backend-architect-e-t-y-b

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backend teams often struggle to design scalable, secure, and maintainable backends across diverse stacks and deployment models. This Skill provides expert guidance on choosing architectures, API design patterns, security, observability, and migration strategies to align with business goals.

Core Features & Use Cases

  • Guidance on architecture decisions spanning monoliths, modular monoliths, and microservices, with multi-language considerations (Java, TypeScript/Node, Go, Python, Rust).
  • Criteria for API design (REST, GraphQL, gRPC), service boundaries, authentication/authorization, governance, and deployment patterns.
  • Practical migration playbooks (e.g., Strangler Fig, phased decompositions), risk management, and observability strategies.

Quick Start

Outline a practical starting architecture and a phased migration plan from monolith to modular microservices tailored to your team's skills.

Frequently Asked Questions about backend-architect

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

FAQPage Schema
How do I migrate a monolith to microservices without downtime?

Migrate a monolith to microservices by applying phased patterns like Strangler Fig to incrementally extract domains. This manages decomposition risk by routing traffic to new bounded services gradually while maintaining the modular monolith until stability is achieved.

What is a modular monolith and when should I use it over microservices?

A modular monolith is a single deployment unit with strictly enforced internal boundaries between domains. Use it over microservices when your team is scaling but lacks the operational maturity for distributed-systems overhead, serving as a stepping stone for future service extraction.

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

Choose between REST, GraphQL, and gRPC by evaluating your client needs and service boundaries. REST suits standard public APIs, GraphQL optimizes flexible client queries, and gRPC enables high-performance internal microservices communication via strongly typed contracts.

Does backend architecture guidance work across Java, Go, and Rust stacks?

Yes, backend architecture guidance applies across Java, TypeScript/Node, Go, Python, and Rust stacks. It covers multi-language considerations for service boundaries, authentication, and deployment patterns to align your distributed-systems design with your team's specific technology choices.

What's the best way to plan observability for distributed systems?

Plan observability for distributed systems by integrating logging, metrics, and tracing across all microservices. Establish comprehensive monitoring during the architecture phase to track service health, diagnose cross-boundary latency, and validate migration strategies effectively.

When should I not use microservices for my backend architecture?

Avoid microservices when your domain logic is tightly coupled or your team lacks dedicated DevOps capacity. If service boundaries are ambiguous, a modular monolith prevents the operational overhead and network latency penalties of premature distributed-systems decomposition.