go-kit VS go-micro

https://github.com/go-kit/kit

. Web backend (with various frameworks available) . Web Assembly (one of them is vugu framework) . Microservices (some frameworks: Go Micro, Go Kit, Gizmo, Kite) . Fragments services (Term mentioned by @jeffotoni in a microservices discussion group) . Lambdas (FaaS example) . Client Server . Terminal applications (using the tview lib) . IoT (some frameworks) . Bots (some here) . Client Applications using Web technology . Desktop using Qt+QML, Native Win Lib (example Qt, Qt widgets, Qml) . Network Applications . Protocol applications . REST Applications . SOAP Applications . GraphQL Applications . RPC Applications . TCP Applications . gRPC Applications . WebSocket Applications . GopherJS (compiles Go to JavaScript)

To implement service discovery in our GoLang microservice we will use GoKit, a toolkit for microservices that provides support to auth, log, service discovery, tracing and more. For this starter code the mod already installed, you can skip this step

My company uses go-kit

For reference my company Go projects are built with (go-kit)[https://gokit.io/] design patterns.

5. kit. The kit framework is a programming toolkit for building robust, reliable, and maintainable microservices in Golang. It is a collection of packages and best practices that offer businesses of all sizes a thorough, reliable, and trustworthy way to create microservices. Go is a fantastic general-purpose language, but microservices need some specialized assistance. As a result, the kit framework offers infrastructure integration, system observability, and Remote Procedure Call (RPC) safety. Golang is a first-class language for creating microservices in any organization thanks to its composition of numerous closely related packages that together form an opinionated framework for building substantial Service-Oriented Architectures (SOAs).It was created with interoperability in mind, and developers are free to select the platforms, databases, components, and architectural styles that best suit their needs. The disadvantage of using go-kit is that it has a high overhead for adding API to the service because of how heavily it relies on interfaces. Documentation Link: https://github.com/go-kit/kit

At first I was confused but this GitHub user/org is completely different from the massively popular go-kit/kit https://github.com/go-kit/kit

https://github.com/go-kit/kit#related-projects

go-micro seems like it does a bit too much, like service discovery and balancing within the framework when that's likely better handled by an Envoy/Istio.

I think the more interesting aspect of this is the framework being used: https://github.com/micro/micro

I haven't dug into it at all yet, but at a glance it looks like it's aiming to do something similar to what Go kit (https://gokit.io/) or Finagle (https://twitter.github.io/finagle/) does, where it gives you a nice abstraction for defining your "service" and then handles all the supplementary aspects (service discovery, serialization, retry/circuit breaker logic, rate limiting, hooks for logging, tracing, and metrics, etc) so you don't have to build those from scratch every time.

I don't know if any of those other frameworks could really be considered very "successful" outside the original organizations they were built for (it seems like the industry has bet more on service meshes and API gateway products), but I'd probably be more inclined to start with one of them than making a new framework.

Had similar goals. Started by writing Go interfaces for it with Go Micro - https://go-micro.dev then opted for the platform service model as you mentioned with Micro - https://micro.dev

I think whether it's Dapr, Micro or something else, the platform service model with well defined interfaces is the way to go. I don't think a lot of people get this yet so it's still going to be a few years before it takes off.

Website: https://github.com/go-micro/go-micro

Good luck Buf! I spent many years building an RPC framework around gRPC called Go Micro (https://github.com/asim/go-micro). I think one of the biggest issues was just resources to see it through but also my own desire to move beyond it towards a platform and services. I hope you're able to bring some sense to the gRPC world. It's mostly a networking library. The ecosystem around it is too low level. If anything abstractions and more developer friendly tooling would be a massive improvement. No one needs to see or touch the guts of gRPC. I wish I didn't have to peak into the internals but unfortunately that's what it takes to integrate it elsewhere.

I hope you build something awesome for the community!

$ github-compare zeromicro/go-zero go-kratos/kratos asim/go-micro go-kit/kit ┌─────────────────────────┬─────────────────────┬───────────────────────┬──────────────────────┬──────────────────┐ │ METRICS │ ZEROMICRO/GO-ZERO │ GO-KRATOS/KRATOS │ ASIM/GO-MICRO │ GO-KIT/KIT │ ├─────────────────────────┼─────────────────────┼───────────────────────┼──────────────────────┼──────────────────┤ │ 🏠 homepage │ https://go-zero.dev │ https://go-kratos.dev │ https://go-micro.dev │ https://gokit.io │ │ 🌎 language │ Go │ Go │ Go │ Go │ │ 📌 license │ MIT License │ MIT License │ Apache License 2.0 │ MIT License │ │ ⏰ age │ 655 days │ 1231 days │ 2688 days │ 2668 days │ │ 🌟 stars │ 17778(27/d) │ 17856(14/d) │ 18233(6/d) │ 23084(8/d) │ │ 📊 latestDayStarCount │ 33 (up) │ 7 (down) │ 2 (down) │ 10 (up) │ │ 📉 latestWeekStarCount │ 227 (up) │ 64 (down) │ 31 (down) │ 44 (down) │ │ 📈 latestMonthStarCount │ 916 │ 531 │ 176 │ 235 │ │ 👏 forks │ 2520(3/d) │ 3446(2/d) │ 2087(0/d) │ 2315(0/d) │ │ 👀 watchers │ 266 │ 424 │ 510 │ 690 │ │ 💪 issues │ 50/741 │ 51/793 │ 76/914 │ 35/548 │ │ 💯 pull requests │ 13/1155 │ 10/1221 │ 0/1513 │ 9/627 │ │ 👥 contributors │ 132 │ 198 │ 166 │ 221 │ │ 🚀 releases │ 63 │ 49 │ 206 │ 12 │ │ 🔭 release circle(avg) │ 10 days │ 25 days │ 13 days │ 222 days │ │ 🎯 lastRelease │ 24 day(s) ago │ 1 day(s) ago │ 5 day(s) ago │ 8 month(s) ago │ │ 🕦 lastCommit │ 2 day(s) ago │ 2 hour(s) ago │ 5 day(s) ago │ 6 day(s) ago │ │ 📝 lastUpdate │ 47 minute(s) ago │ 16 minute(s) ago │ 1 hour(s) ago │ 1 hour(s) ago │ └─────────────────────────┴─────────────────────┴───────────────────────┴──────────────────────┴──────────────────┘