Go kit: the road ahead

# Go kit: the road ahead - This is a tracking issue for broad changes to the Go kit project - Expect edits and updates - No ETA at this time ### Context - The microservices ecosystem has matured since Go kit's introduction - Many responsibilities have, sensibly, moved to the platform/infrastructure - Go kit has, accordingly, reduced its scope of responsibilities in practice - Go kit is less about specific components or integrations, more about good application architecture - The next iteration of the project should reflect this reality - Keep and refocus on the good and useful parts, deprecate the less-useful parts ### Keep - package transport - necessary and valuable - package endpoint - required for service/transport interop, pending generics - package log - has clearly proved its value in the test of time - package tracing - has also proved its value - package examples - move to new or individual repos ### Undecided - package metrics - pending broader re-think and refactor - kitgen - ownership is unclear - package auth - I can't easily judge usefulness; seeking comment ### Sunset - package ratelimit - less useful in modern platforms, easy to bolt-on with generic middleware - package circuitbreaker - less useful in modern platforms, easy to bolt-on with generic middleware - package sd - less useful in modern platforms, many test flakes, a maintenance headache ### Additional changes - Rewrite website with new focus on architectural design and best practice - New,

Posted by peterbourgon on Mar 4, 2019, 10:05 PM

Tags

• github (Other)

Related issues

• struct's lifetime requirements can be bypassed via covariant field assignment
• Proposal to Reorganize the Moderation Team and Review Moderation Policies
• Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
• proposal: container/...: generic collection types
• Better Custom Endpoint BYOK
• A concrete policy for backward compatibility until Godot 5.0