Communitygithub.com

Padrões de Backend

Padrões de arquitetura de backend, design de API, otimização de banco de dados e melhores práticas do lado do servidor para Node.js, Express e rotas de API do Next.js. Use ao construir ou revisar rotas de API Node.js, Express ou Next.js e seu acesso a dados.

O que é Padrões de Backend?

Esta skill fornece um guia completo de padrões de arquitetura de backend e melhores práticas para construir aplicações server-side escaláveis, com foco em Node.js, Express e Next.js. Ela abrange desde o design de APIs RESTful e GraphQL, passando pela implementação dos padrões Repository, Service Layer e Middleware, até otimizações de banco de dados como prevenção do problema N+1 e uso de transações. A skill também inclui estratégias de caching com Redis, tratamento centralizado de erros com retry e backoff exponencial, autenticação JWT e controle de acesso baseado em papéis (RBAC). O conteúdo é apresentado com exemplos de código práticos em TypeScript e SQL, e recomenda o uso de armazenamento compartilhado (como Redis) para rate limiting em produção, sendo ideal para desenvolvedores que desejam estruturar backends mais robustos e de fácil manutenção.

Funciona com~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/affaan-m/everything-claude-code/tree/main/skills/backend-patterns

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

Padrões de Desenvolvimento de Backend

Padrões de arquitetura de backend e melhores práticas para aplicações server-side escaláveis.

Quando Ativar

  • Projetando endpoints de API REST ou GraphQL
  • Implementando camadas de repositório, serviço ou controlador
  • Otimizando consultas de banco de dados (N+1, indexação, pool de conexões)
  • Adicionando cache (Redis, em memória, cabeçalhos de cache HTTP)
  • Configurando jobs em segundo plano ou processamento assíncrono
  • Estruturando tratamento de erros e validação para APIs
  • Construindo middleware (autenticação, logging, rate limiting)

Padrões de Design de API

Estrutura de API RESTful

// CORRETO: URLs baseadas em recursos
GET    /api/markets                 # Listar recursos
GET    /api/markets/:id             # Obter recurso único
POST   /api/markets                 # Criar recurso
PUT    /api/markets/:id             # Substituir recurso
PATCH  /api/markets/:id             # Atualizar recurso
DELETE /api/markets/:id             # Excluir recurso

// CORRETO: Parâmetros de consulta para filtragem, ordenação, paginação
GET /api/markets?status=active&sort=volume&limit=20&offset=0

Padrão de Repositório

// Abstrair a lógica de acesso a dados
interface MarketRepository {
  findAll(filters?: MarketFilters): Promise<Market[]>;
  findById(id: string): Promise<Market | null>;
  create(data: CreateMarketDto): Promise<Market>;
  update(id: string, data: UpdateMarketDto): Promise<Market>;
  delete(id: string): Promise<void>;
}

class SupabaseMarketRepository implements MarketRepository {
  async findAll(filters?: MarketFilters): Promise<Market[]> {
    let query = supabase.from('markets').select('*');

    if (filters?.status) {
      query = query.eq('status', filters.status);
    }

    if (filters?.limit) {
      query = query.limit(filters.limit);
    }

    const { data, error } = await query;

    if (error) throw new Error(error.message);
    return data;
  }

  // Outros métodos...
}

Padrão de Camada de Serviço

// Lógica de negócios separada do acesso a dados
class MarketService {
  constructor(private marketRepo: MarketRepository) {}

  async searchMarkets(query: string, limit: number = 10): Promise<Market[]> {
    // Lógica de negócio
    const embedding = await generateEmbedding(query);
    const results = await this.vectorSearch(embedding, limit);

    // Buscar dados completos
    const markets = await this.marketRepo.findByIds(results.map(r => r.id));

    // Ordenar por similaridade
    return markets.sort((a, b) => {
      const scoreA = results.find(r => r.id === a.id)?.score || 0;
      const scoreB = results.find(r => r.id === b.id)?.score || 0;
      return scoreA - scoreB;
    });
  }

  private async vectorSearch(embedding: number[], limit: number) {
    // Implementação de busca vetorial
  }
}

Padrão de Middleware

// Pipeline de processamento de requisição/resposta
export function withAuth(handler: NextApiHandler): NextApiHandler {
  return async (req, res) => {
    const token = req.headers.authorization?.replace('Bearer ', '');

    if (!token) {
      return res.status(401).json({ error: 'Não autorizado' });
    }

    try {
      const user = await verifyToken(token);
      req.user = user;
      return handler(req, res);
    } catch (error) {
      return res.status(401).json({ error: 'Token inválido' });
    }
  };
}

// Uso
export default withAuth(async (req, res) => {
  // O handler tem acesso a req.user
});

Padrões de Banco de Dados

Otimização de Consultas

// CORRETO: Selecionar apenas as colunas necessárias
const { data } = await supabase
  .from('markets')
  .select('id, name, status, volume')
  .eq('status', 'active')
  .order('volume', { ascending: false })
  .limit(10);

// ERRADO: Selecionar tudo
const { data } = await supabase
  .from('markets')
  .select('*');

Prevenção do Problema N+1

// ERRADO: Problema de consulta N+1
const markets = await getMarkets();
for (const market of markets) {
  market.creator = await getUser(market.creator_id);  // N consultas
}

// CORRETO: Busca em lote
const markets = await getMarkets();
const creatorIds = markets.map(m => m.creator_id);
const creators = await getUsers(creatorIds);  // 1 consulta
const creatorMap = new Map(creators.map(c => [c.id, c]));

markets.forEach(market => {
  market.creator = creatorMap.get(market.creator_id);
});

Padrão de Transação

async function createMarketWithPosition(
  marketData: CreateMarketDto,
  positionData: CreatePositionDto
) {
  // Usar transação do Supabase
  const { data, error } = await supabase.rpc('create_market_with_position', {
    market_data: marketData,
    position_data: positionData
  });

  if (error) throw new Error('Transação falhou');
  return data;
}

// Função SQL no Supabase
CREATE OR REPLACE FUNCTION create_market_with_position(
  market_data jsonb,
  position_data jsonb
)
RETURNS jsonb
LANGUAGE plpgsql
AS $$
BEGIN
  -- Iniciar transação automaticamente
  INSERT INTO markets VALUES (market_data);
  INSERT INTO positions VALUES (position_data);
  RETURN jsonb_build_object('success', true);
EXCEPTION
  WHEN OTHERS THEN
    -- Rollback ocorre automaticamente
    RETURN jsonb_build_object('success', false, 'error', SQLERRM);
END;
$$;

Estratégias de Cache

Camada de Cache com Redis

class CachedMarketRepository implements MarketRepository {
  constructor(
    private baseRepo: MarketRepository,
    private redis: RedisClient
  ) {}

  async findById(id: string): Promise<Market | null> {
    // Verificar cache primeiro
    const cached = await this.redis.get(`market:${id}`);

    if (cached) {
      return JSON.parse(cached);
    }

    // Erro de cache - buscar do banco de dados
    const market = await this.baseRepo.findById(id);

    if (market) {
      // Armazenar em cache por 5 minutos
      await this.redis.setex(`market:${id}`, 300, JSON.stringify(market));
    }

    return market;
  }

  async invalidateCache(id: string): Promise<void> {
    await this.redis.del(`market:${id}`);
  }
}

Padrão Cache-Aside

async function getMarketWithCache(id: string): Promise<Market> {
  const cacheKey = `market:${id}`;

  // Tentar cache
  const cached = await redis.get(cacheKey);
  if (cached) return JSON.parse(cached);

  // Erro de cache - buscar do BD
  const market = await db.markets.findUnique({ where: { id } });

  if (!market) throw new Error('Mercado não encontrado');

  // Atualizar cache
  await redis.setex(cacheKey, 300, JSON.stringify(market));

  return market;
}

Padrões de Tratamento de Erros

Manipulador de Erros Centralizado

class ApiError extends Error {
  constructor(
    public statusCode: number,
    public message: string,
    public isOperational = true
  ) {
    super(message);
    Object.setPrototypeOf(this, ApiError.prototype);
  }
}

export function errorHandler(error: unknown, req: Request): Response {
  if (error instanceof ApiError) {
    return NextResponse.json({
      success: false,
      error: error.message
    }, { status: error.statusCode });
  }

  if (error instanceof z.ZodError) {
    return NextResponse.json({
      success: false,
      error: 'Falha na validação',
      details: error.issues
    }, { status: 400 });
  }

  // Log de erros inesperados
  console.error('Erro inesperado:', error);

  return NextResponse.json({
    success: false,
    error: 'Erro interno do servidor'
  }, { status: 500 });
}

// Uso
export async function GET(request: Request) {
  try {
    const data = await fetchData();
    return NextResponse.json({ success: true, data });
  } catch (error) {
    return errorHandler(error, request);
  }
}

Retry com Backoff Exponencial

async function fetchWithRetry<T>(
  fn: () => Promise<T>,
  maxRetries = 3
): Promise<T> {
  let lastError: Error;

  for (let i = 0; i < maxRetries; i++) {
    try {
      return await fn();
    } catch (error) {
      lastError = error as Error;

      if (i < maxRetries - 1) {
        // Backoff exponencial: 1s, 2s, 4s
        const delay = Math.pow(2, i) * 1000;
        await new Promise(resolve => setTimeout(resolve, delay));
      }
    }
  }

  throw lastError!;
}

// Uso
const data = await fetchWithRetry(() => fetchFromAPI());

Autenticação e Autorização

Validação de Token JWT

import jwt from 'jsonwebtoken';

interface JWTPayload {
  userId: string;
  email: string;
  role: 'admin' | 'user';
}

export function verifyToken(token: string): JWTPayload {
  try {
    const payload = jwt.verify(token, process.env.JWT_SECRET!) as JWTPayload;
    return payload;
  } catch (error) {
    throw new ApiError(401, 'Token inválido');
  }
}

export async function requireAuth(request: Request) {
  const token = request.headers.get('authorization')?.replace('Bearer ', '');

  if (!token) {
    throw new ApiError(401, 'Token de autorização ausente');
  }

  return verifyToken(token);
}

// Uso em rota de API
export async function GET(request: Request) {
  const user = await requireAuth(request);

  const data = await getDataForUser(user.userId);

  return NextResponse.json({ success: true, data });
}

Controle de Acesso Baseado em Papéis (RBAC)

type Permission = 'read' | 'write' | 'delete' | 'admin';

interface User {
  id: string;
  role: 'admin' | 'moderator' | 'user';
}

const rolePermissions: Record<User['role'], Permission[]> = {
  admin: ['read', 'write', 'delete', 'admin'],
  moderator: ['read', 'write', 'delete'],
  user: ['read', 'write']
};

export function hasPermission(user: User, permission: Permission): boolean {
  return rolePermissions[user.role].includes(permission);
}

export function requirePermission(permission: Permission) {
  return (handler: (request: Request, user: User) => Promise<Response>) => {
    return async (request: Request) => {
      const user = await requireAuth(request);

      if (!hasPermission(user, permission)) {
        throw new ApiError(403, 'Permissões insuficientes');
      }

      return handler(request, user);
    };
  };
}

// Uso - HOF envolve o handler
export const DELETE = requirePermission('delete')(
  async (request: Request, user: User) => {
    // Handler recebe o usuário autenticado com permissão verificada
    return new Response('Excluído', { status: 200 });
  }
);

Rate Limiting

O rate limiting deve usar um armazenamento compartilhado como Redis, um gateway ou o limitador nativo da plataforma. Não use contadores em memória por processo para APIs de produção: eles resetam na implantação, são divididos entre réplicas e falham abertamente em ambientes serverless ou multi-instância.

Mantenha a camada de backend responsável por escolher o ponto de integração e a forma do erro; use api-design para o contrato HTTP e security-review para revisão de casos de abuso.

Jobs em Segundo Plano e Filas

Padrão de Fila Simples

class JobQueue<T> {
  private queue: T[] = [];
  private processing = false;

  async add(job: T): Promise<void> {
    this.queue.push(job);

    if (!this.processing) {
      this.process();
    }
  }

  private async process(): Promise<void> {
    this.processing = true;

    while (this.queue.length > 0) {
      const job = this.queue.shift()!;

      try {
        await this.execute(job);
      } catch (error) {
        console.error('Job falhou:', error);
      }
    }

    this.processing = false;
  }

  private async execute(job: T): Promise<void> {
    // Lógica de execução do job
  }
}

// Uso para indexação de mercados
interface IndexJob {
  marketId: string;
}

const indexQueue = new JobQueue<IndexJob>();

export async function POST(request: Request) {
  const { marketId } = await request.json();

  // Adicionar à fila em vez de bloquear
  await indexQueue.add({ marketId });

  return NextResponse.json({ success: true, message: 'Job enfileirado' });
}

Logging e Monitoramento

Logging Estruturado

interface LogContext {
  userId?: string;
  requestId?: string;
  method?: string;
  path?: string;
  [key: string]: unknown;
}

class Logger {
  log(level: 'info' | 'warn' | 'error', message: string, context?: LogContext) {
    const entry = {
      timestamp: new Date().toISOString(),
      level,
      message,
      ...context
    };

    console.log(JSON.stringify(entry));
  }

  info(message: string, context?: LogContext) {
    this.log('info', message, context);
  }

  warn(message: string, context?: LogContext) {
    this.log('warn', message, context);
  }

  error(message: string, error: Error, context?: LogContext) {
    this.log('error', message, {
      ...context,
      error: error.message,
      stack: error.stack
    });
  }
}

const logger = new Logger();

// Uso
export async function GET(request: Request) {
  const requestId = crypto.randomUUID();

  logger.info('Buscando mercados', {
    requestId,
    method: 'GET',
    path: '/api/markets'
  });

  try {
    const markets = await fetchMarkets();
    return NextResponse.json({ success: true, data: markets });
  } catch (error) {
    logger.error('Falha ao buscar mercados', error as Error, { requestId });
    return NextResponse.json({ error: 'Erro interno' }, { status: 500 });
  }
}

Lembre-se: Padrões de backend permitem aplicações server-side escaláveis e de fácil manutenção. Escolha os padrões que se adequam ao seu nível de complexidade.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

accessibility

Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA. Use when building or auditing UI that must meet WCAG 2.2 Level AA, or when reviewing a change for keyboard, contrast, or screen-reader support.

affaan-m/claude-api

Anthropic Claude API patterns for Python and TypeScript. Covers Messages API, streaming, tool use, vision, extended thinking, batches, prompt caching, and Claude Agent SDK. Use when building applications with the Claude API or Anthropic SDKs.

affaan-m/everything-claude-code

End-to-end marketing campaign planning and execution. Covers audience research, positioning, campaign angle definition, landing page copy, email sequences, social posts, ad copy, short-form video scripts, and content calendars. Use as the orchestration layer for multi-channel product launches. Use when planning or executing a multi-channel product launch, or producing landing page, email, social, or ad copy.

affaan-m/everything-claude-code

Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

affaan-m/everything-claude-code-conventions

Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

affaan-m/frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build web components, pages, or applications and the visual direction matters as much as the code quality.

affaan-m/gget

gget CLI and Python workflow for quick genomic database queries, sequence lookup, BLAST-style searches, enrichment checks, and reproducible bioinformatics evidence logs.

affaan-m/literature-review

Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.

affaan-m/motion-ui

Production-ready UI motion system for React/Next.js. Use when implementing animations, transitions, or motion patterns.

affaan-m/project-guidelines-example

Example project-specific skill template based on a real production application.

affaan-m/pubmed-database

Direct PubMed and NCBI E-utilities search workflows for biomedical literature, MeSH queries, PMID lookup, citation retrieval, and API-backed literature monitoring.

affaan-m/scholar-evaluation

Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.

affaan-m/uspto-database

USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.

agent-architecture-audit

Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first fixes. Essential for developers building agent applications, autonomous loops, or any LLM-powered feature. Use when an agent or LLM feature misbehaves and the failing layer is unknown, or before shipping an agent stack.

agent-eval

Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics. Use when choosing between coding agents, or when a change to an agent setup needs measured pass rate, cost, and time rather than an impression.

agent-harness-construction

Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates. Use when defining or revising an agent

agentic-engineering

Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing. Use when planning or executing engineering work that agents will carry out end to end.

agentic-os

Build persistent multi-agent operating systems on Claude Code. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases. Use when building a persistent multi-agent system on Claude Code with its own memory, commands, and scheduling.

agent-introspection-debugging

Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.

agent-payment-x402

Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk and X Layer through OKX Payments / OKX Agent Payments Protocol. Use when an agent must pay for something itself and needs per-task budgets, spending controls, and a non-custodial wallet.

Habilidades Relacionadas