GoWind Framework

The GoWind framework is a building-block Go microservices framework consisting of three layers: the core framework go-wind, the plugin ecosystem go-wind-plugins, and the declarative bootstrap go-wind-bootstrap. It provides complete infrastructure ranging from low-level lifecycle management to declarative, configuration-driven startup.

1. The Three Projects

Recent additions: the go-wind core now provides two lifecycle hooks, beforeStart and afterStart, offering extension points before and after application startup (see App Lifecycle Management); the CodeToHTTP function in the errors package supports explicitly passing error codes 400–599 through as HTTP status codes.

2. Design Philosophy

2.1 Building-Block Architecture

Not an all-in-one full-stack framework, but a box of building blocks.

• Composition over inheritance — each plugin only implements standard interfaces; business code depends on interfaces rather than implementations
• Interfaces over implementations — the core only defines minimal interfaces; concrete implementations are provided by plugins
• Zero hidden magic — all behavior is explicit, with no implicit initialization or global state

2.2 Layered Responsibilities

2.3 Zero External Dependencies

The core framework depends only on golang.org/x/sync and introduces no third-party libraries.

3. Plugin Domain Overview

Built on unified abstractions across eight major domains with multi-engine adaptation, go-wind-plugins currently contains 157 independent go.mod modules, roughly 130+ plugins, covering 20+ domains:

In addition, it covers domains such as circuit breaking (4), rate limiting (3), workflow engines (Temporal/Argo/Conductor/GoWorkflows), object storage (2), AI integration (OpenAI/LangChainGo/Eino), metrics monitoring (Prometheus etc.), distributed tracing (OTLP), and utilities (4) — 20+ domains in total.

Recent developments: the MCP transport now passes through StreamableHTTP/SSE server options; a new vector abstraction connects to four vector/graph databases — qdrant/milvus/neo4j/weaviate; selector client-side load balancing plus a resolver gRPC adapter; and the transaction local-transaction quartet (outbox/saga/tcc/xa).

4. Quick Start

4.1 Installation

go get github.com/tx7do/go-wind
go get github.com/tx7do/go-wind-bootstrap

4.2 Minimal Example

package main

import (
    "github.com/tx7do/go-wind"
    _ "github.com/tx7do/go-wind-plugins/transport/http"    // Import the HTTP plugin
    _ "github.com/tx7do/go-wind-plugins/log/zap"           // Import the Zap logging plugin
    "github.com/tx7do/go-wind-bootstrap"
)

func main() {
    // One-line startup: read YAML configuration and assemble all components
    bootstrap.RunApp()
}

4.3 Configuration File

# app.yaml
name: my-service

servers:
  - name: http
    type: http
    addr: ":8080"

log:
  level: info
  format: json

registry:
  type: etcd
  config:
    endpoints: ["localhost:2379"]

5. Relationship with Business Applications

6. Related Documentation

Fundamentals

• Framework Architecture

go-wind Core

• Core Framework Introduction
• App Lifecycle Management
• Context Propagation
• Transport Abstraction
• Log Facade Interface

go-wind-plugins

• Plugin Ecosystem Overview
• Configuration Center
• Service Registry
• Log Adapters
• Transport Protocols
• Message Queues
• Encoding
• Security
• Distributed Tracing
• Cache
• Object Storage
• Rate Limiting and Circuit Breaking
• Metrics Monitoring
• AI Integration
• Workflow Engines

go-wind-bootstrap

• Declarative Bootstrap Introduction
• BootstrapConfig Definition
• SPI Plugin Registration Mechanism
• Declarative Middleware Orchestration
• Cobra CLI Integration
• Complete Examples

Tutorials