Skip to content

henriqueatila/golang-gin-best-practices / skills/golang-gin-architect

golang-gin-architect

Verified

Software architect for Go Gin APIs. Use when making architecture decisions, evaluating complexity, designing systems, choosing patterns, or coordinating across gin skills.

FileKindSize
SKILL.mdskill md10.7 KB
metadata.jsonconfig466 B
references/adr-format-and-templates.mdmarkdown4.1 KB
references/adr-service-extraction-and-example.mdmarkdown4.0 KB
references/api-design-error-contract-docs.mdmarkdown1.8 KB
references/api-design-filtering-bulk-evolution.mdmarkdown3.8 KB
references/api-design-versioning-pagination.mdmarkdown4.3 KB
references/clean-architecture-feature-module.mdmarkdown4.5 KB
references/clean-architecture-layers-di.mdmarkdown5.2 KB
references/complexity-assessment-budget.mdmarkdown5.6 KB
references/complexity-assessment-gates.mdmarkdown4.2 KB
references/complexity-assessment-patterns.mdmarkdown5.0 KB
references/cross-cutting-health-checks.mdmarkdown1.7 KB
references/cross-cutting-observability.mdmarkdown3.9 KB
references/cross-cutting-security-config.mdmarkdown4.4 KB
references/data-ownership-boundaries.mdmarkdown4.5 KB
references/data-ownership-sync-migration.mdmarkdown4.3 KB
references/data-patterns-cqrs.mdmarkdown3.8 KB
references/data-patterns-event-sourcing-aggregate.mdmarkdown2.2 KB
references/data-patterns-event-store.mdmarkdown3.7 KB
references/data-patterns-outbox.mdmarkdown3.7 KB
references/data-patterns-read-replicas.mdmarkdown2.6 KB
references/data-patterns-saga.mdmarkdown3.6 KB
references/error-flow-domain-layers.mdmarkdown5.3 KB
references/error-flow-handler-chain.mdmarkdown4.7 KB
references/golden-main-medium-project.mdmarkdown3.0 KB
references/golden-main-medium-startup.mdmarkdown2.8 KB
references/golden-main-small-project.mdmarkdown4.0 KB
references/grpc-interop-gateway-docker.mdmarkdown2.1 KB
references/grpc-interop-server-client.mdmarkdown2.7 KB
references/grpc-interop-setup.mdmarkdown3.6 KB
references/messaging-consumer-docker.mdmarkdown1.6 KB
references/messaging-consumer-workqueues.mdmarkdown3.6 KB
references/messaging-dlq-idempotency.mdmarkdown3.1 KB
references/messaging-dlq-setup.mdmarkdown2.4 KB
references/messaging-pubsub-exchanges.mdmarkdown3.6 KB
references/messaging-rabbitmq-connection.mdmarkdown3.2 KB
references/messaging-rabbitmq-producer.mdmarkdown2.4 KB
references/object-storage-download-presign.mdmarkdown3.5 KB
references/object-storage-multipart-minio.mdmarkdown2.2 KB
references/object-storage-setup-upload.mdmarkdown4.2 KB
references/redis-cache-warming-pubsub.mdmarkdown3.2 KB
references/redis-caching-patterns.mdmarkdown4.3 KB
references/redis-session-distributed-lock.mdmarkdown3.9 KB
references/resilience-circuit-breaker-bulkhead.mdmarkdown4.3 KB
references/resilience-retry-rate-limiting.mdmarkdown4.0 KB
references/skill-orchestration-overview.mdmarkdown3.2 KB
references/skill-orchestration-workflows.mdmarkdown5.4 KB
references/system-design-bounded-contexts.mdmarkdown4.1 KB
references/system-design-c4-model.mdmarkdown4.6 KB
references/system-design-dependency-graphs.mdmarkdown2.6 KB
references/system-design-domain-modeling.mdmarkdown3.5 KB
references/system-design-project-structure.mdmarkdown4.2 KB
references/tech-debt-identification-prioritization.mdmarkdown5.1 KB
references/tech-debt-refactoring-communication.mdmarkdown4.0 KB

references/complexity-assessment-gates.md

View on GitHub
# Complexity Assessment — You Don't Need This Yet (Gates)

For each high-complexity pattern, ALL listed conditions must be true before adoption is justified. If any are false, use the simpler alternative.

---

## Microservices

All 5 must be true:

- [ ] You have 3+ independent teams that need to deploy on different schedules and are currently blocked
- [ ] You have measured (not estimated) that a specific module has an independent scaling bottleneck
- [ ] You have working distributed tracing across all services (not just logging)
- [ ] You have a CI/CD pipeline that can build, test, and deploy each service independently in under 10 minutes
- [ ] You have on-call runbooks for each service and a tested rollback procedure

**If any is false:** Build a modular monolith. Clean internal package boundaries give you 80% of the benefit at 10% of the cost.

---

## CQRS

All 4 must be true:

- [ ] Read volume is measurably 10x+ write volume (check your query logs)
- [ ] The read model requires data that is inconvenient to compute at query time (multiple joins, aggregations)
- [ ] You have profiled PostgreSQL and confirmed it is the bottleneck — not your Go code or network
- [ ] Your team has built CQRS before and understands eventual consistency implications

**If any is false:** Add a read-optimized query method to your repository. A well-indexed PostgreSQL view handles most "CQRS-shaped problems" without the overhead.

---

## Event Sourcing

All 4 must be true:

- [ ] You have a legal or compliance requirement to reproduce system state at any past point in time
- [ ] Your domain has complex state machines where the transition history matters, not just current state
- [ ] Your team has operational experience running an event store (Kafka, EventStoreDB) in production
- [ ] You have designed your aggregates and projections and the team agrees on the boundaries

**If any is false:** Use a PostgreSQL append-only audit log + standard CRUD domain model.

```sql
-- Handles 90% of audit requirements with 10% of event sourcing complexity:
CREATE TABLE audit_log (
    id         UUID PRIMARY KEY DEFAULT gen_random_uuid(),
    table_name TEXT NOT NULL,
    record_id  TEXT NOT NULL,
    action     TEXT NOT NULL,  -- INSERT, UPDATE, DELETE
    old_values JSONB,
    new_values JSONB,
    actor_id   TEXT,
    created_at TIMESTAMPTZ DEFAULT now()
);
```

---

## Service Mesh (Istio, Linkerd)

All 3 must be true:

- [ ] You have 10+ services in production with active traffic
- [ ] You have a dedicated platform engineer who owns the mesh configuration
- [ ] You have a compliance requirement for mTLS between services that cannot be satisfied by application-level TLS

**If any is false:** Handle TLS at the load balancer, use OpenTelemetry for observability, implement circuit breakers at the application layer.

---

## Distributed Tracing (OpenTelemetry)

You need this when:

- [ ] You have 2+ services communicating with each other
- [ ] You are debugging latency issues that cross service boundaries
- [ ] Structured logging alone cannot explain where time is being spent

**If any is false:** Structured logging with `log/slog` + request IDs is sufficient for a monolith.

---

## Saga / Orchestration

All 4 must be true:

- [ ] A business transaction spans 3+ services or databases
- [ ] Each step can fail independently after already partially committing
- [ ] You need compensating actions that can't be expressed as a single DB rollback
- [ ] Calling services sequentially with manual compensation is insufficient for your retry/durability requirements

**If any is false:** Use a database transaction (single DB) or sequential calls with explicit compensation (2 services).

---

## Message Queue (RabbitMQ, SQS, Kafka)

You need this when:

- [ ] The caller does not need the result immediately
- [ ] The work can fail and be retried later (retry-later semantics)
- [ ] Volume exceeds 1K/min OR durability across process restarts is required

**If any is false:** Use a goroutine + buffered channel for fire-and-forget work.

---

## Final Rule

> Architecture is not a competition. The system that ships, that the team can maintain, and that can be extended by a new hire in their first week — that is the right architecture. Complexity is a debt. Spend it wisely.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 323kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall