micro--go-micro
Asim Aslam
c7657f73f4
goreleaser / goreleaser (push) Has been cancelled
* test(harness): read agent plan from the scoped store
The store-scoping change moved an agent's plan from the default table
key agent/{name}/plan to its own table (database "agent", table {name},
key "plan"). The plan-delegate harness tests still read the old key and
failed with 'not found'; read through store.Scope(mem, "agent", name)
like the agent does.
* docs: orient agents-first across README, landing, and docs overview
Lead with agents (then services and flows), surface MCP + A2A as the
interop story, and frame agents as services. Landing hero and feature
grid reordered agents-first with an A2A gateway card.
* v6: module path go-micro.dev/v6, TLS secure by default, NewService
Cut v6. Three breaking changes, bundled so the major bump is paid once:
- Module path go-micro.dev/v5 -> go-micro.dev/v6 across all imports + go.mod.
- TLS verification on by default (was off). MICRO_TLS_SECURE removed;
MICRO_TLS_INSECURE=true opts out for self-signed/dev.
- micro.NewService(name, opts...) is the canonical service constructor,
symmetric with NewAgent/NewFlow; micro.New kept as a deprecated alias;
the old name-less NewService(opts...) removed. Generators emit NewService.
Also ports the JWT auth token provider in-module (go-micro.dev/v6/auth/jwt/token
on golang-jwt/jwt/v5), dropping the v5-pinned github.com/micro/plugins/v5/auth/jwt
and the deprecated dgrijalva/jwt-go.
Docs/README/landing updated to v6 and @latest; v5->v6 migration guide added;
CHANGELOG cut as [6.0.0]. Blog posts left at their historical versions.
---------
Co-authored-by: Claude <noreply@anthropic.com>
1.4 KiB
1.4 KiB
layout
| layout |
|---|
| default |
Migration Guides
Step-by-step guides for migrating to Go Micro from other frameworks.
Available Guides
- v5 to v6 - Upgrade to v6: new module path, TLS secure by default,
NewService - Add MCP to Existing Services - Make your services AI-accessible in 5 minutes
- From gRPC - Migrate from gRPC to Go Micro with minimal code changes
Coming Soon
We're working on additional migration guides:
- From go-kit - Migrate from Go kit microservices framework
- From Standard Library - Upgrade from net/http and net/rpc
- From Gin/Echo - Transition from HTTP-only frameworks
- From Micro v3 - Upgrade from older Go Micro versions
Why Migrate to Go Micro?
- Pluggable Architecture - Swap components without changing code
- Zero Configuration - Works out of the box with sensible defaults
- Progressive Enhancement - Start simple, add complexity when needed
- Unified Abstractions - Registry, transport, broker, store all integrated
- Active Development - Regular updates and community support
Need Help?
- Check the Framework Comparison guide
- Review Architecture Decisions to understand design choices
- Ask questions in GitHub Discussions
- See the Contributing Guide to contribute new migration guides