4 ms·

I think the more interesting aspect of this is the framework being used: https://github.com/micro/micro https://github.com/micro/micro I haven't dug into it at

I think the more interesting aspect of this is the framework being used: https://github.com/micro/micro 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/ https://gokit.io/) or Finagle (https://twitter.github.io/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.

asim 4y ago
I spent quite a few years working on a standalone framework called Go Micro which has now been donated to a community - https://github.com/go-micro/go-micro https://github.com/go-micro/go-micro. Ultimately it never really achieved the potential standardisation I was hoping for e.g something like gRPC. Micro is more of an all encompassing platform that addresses not just writing code but running, consuming it, securing it. I've been using it in production for 3-4 years now after a lot of pure OSS development. Still as others are saying it may never reach its true potential without the backing of a big vendor.