Adr 001 Plugin Architecture
Microservices frameworks need to support multiple infrastructure backends (registries, brokers, transports, stores). Different teams have different preferences and existing infrastructure.
Architecture Decision Records
Documentation of architectural decisions made in Go Micro, following the ADR pattern.
What are ADRs?
Architecture Decision Records (ADRs) capture important architectural decisions along with their context and consequences. They help understand why certain design choices were made.
Planned
Core Design
- ADR-002: Interface-First Design
- ADR-003: Default Implementations
Service Discovery
- ADR-005: Registry Plugin Scope
Communication
- ADR-006: HTTP as Default Transport
- ADR-007: Content-Type Based Codecs
Configuration
- ADR-008: Environment Variable Support
Status Values
- Proposed: Under consideration
- Accepted: Decision approved
- Deprecated: No longer recommended
- Superseded: Replaced by another ADR
Contributing
To propose a new ADR:
- Number it sequentially (check existing ADRs)
- Follow the structure of existing ADRs
- Include: Status, Context, Decision, Consequences, Alternatives
- Submit a PR for discussion
- Update status based on review
ADRs are immutable once accepted. To change a decision, create a new ADR that supersedes the old one.
Adr 004 Mdns Default Registry
Service discovery is critical for microservices. Common approaches:
Adr 009 Progressive Configuration
Microservices frameworks face a paradox:
Adr 010 Unified Gateway
Authors: Go Micro Team
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.