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/system-design-bounded-contexts.md

View on GitHub
# System Design — Bounded Context Analysis

When and how to identify bounded contexts in Go Gin APIs.

Companion to `system-design-domain-modeling.md` (entities with behavior, value objects).

> **Default stance:** Skip domain modeling for simple CRUD. Use these tools when complexity is real and measured.

---

## When to Use

- You have a "God model" — one `User` struct imported everywhere, growing to 40+ fields
- Different teams argue about what fields belong in a shared struct
- Changing one part of the domain model breaks unrelated features
- You're evaluating whether to extract a module into a separate service

Skip it when you have a simple app with one team and < 10 domain entities.

---

## Identifying Implicit Bounded Contexts

Symptoms of implicit bounded contexts inside a monolith:

- The word "User" means different things in different features (auth = credentials+roles; billing = payment methods; notification = email+push token)
- Package A and Package B both define a `Product` struct with different fields
- You have a `types` or `models` package that everything imports — and it keeps growing
- Merge conflicts regularly happen in the same files for unrelated features

---

## How to Find Your Bounded Contexts

1. **Noun workshop:** List every noun (entity/concept) in the domain.
2. **Group by team/feature ownership:** Which nouns naturally cluster together?
3. **Identify ubiquitous language:** Do "User" and "Customer" mean the same thing in all clusters?
4. **Look at change frequency:** Files that always change together are in the same context.
5. **Find the seams:** Where do contexts communicate? Those are your integration points — model them as interfaces.

---

## Package Boundary Design

```go
// internal/order/ports.go
// "ports" = interfaces this module needs from outside
package order

import "context"

// UserLookup is order's view of what it needs from the user domain.
// Defined HERE (order module owns its dependencies), not in internal/user.
type UserLookup interface {
    GetByID(ctx context.Context, id string) (UserInfo, error)
}

// UserInfo is order's projection — NOT the full user domain model.
// Adding a field to user.User does NOT require changing this struct.
type UserInfo struct {
    ID    string
    Name  string
    Email string
}
```

```go
// internal/order/service.go
package order

type Service struct {
    repo   Repository
    users  UserLookup  // injected — order doesn't care about the concrete type
    logger *slog.Logger
}

func NewService(repo Repository, users UserLookup, logger *slog.Logger) *Service {
    return &Service{repo: repo, users: users, logger: logger}
}
```

---

## Context Mapping Patterns (Lightweight)

| Pattern | Use when | Go implementation |
|---|---|---|
| **Shared Kernel** | Two modules share a small, stable set of types (e.g., `Money`, `Address`) | `internal/shared/` package — kept tiny, changes require both teams to agree |
| **Anti-Corruption Layer** | Integrating with an external system whose model you don't control (Stripe, external ERP) | Adapter struct in `internal/[domain]/adapters/` |
| **Conformist** | Downstream consumer of an upstream API, too costly to translate | Accept their model, document the dependency explicitly |

```go
// Anti-corruption layer: Stripe payment intent → internal PaymentResult
// internal/billing/adapters/stripe_adapter.go
package adapters

type StripeAdapter struct{ client *stripe.Client }

func (a *StripeAdapter) Charge(amount int64, currency, token string) (*billing.PaymentResult, error) {
    pi, err := a.client.PaymentIntents.New(nil)
    if err != nil {
        return nil, fmt.Errorf("stripe charge: %w", err)
    }
    return &billing.PaymentResult{
        TransactionID: pi.ID,
        Amount:        amount,
        Status:        translateStatus(pi.Status),
    }, nil
}
```

---

## Cross-Skill References

- For domain modeling (entities, value objects): see **[system-design-domain-modeling.md](system-design-domain-modeling.md)**
- For project structure by scale: see **[system-design-project-structure.md](system-design-project-structure.md)**
- For C4 diagrams: see **[system-design-c4-model.md](system-design-c4-model.md)**
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: 322kUpdated 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