micro VS go-zero

Hey all

I'm Asim. I'm an engineer who's been hacking on an open source project called Micro for the past eight years (https://micro.dev). In that time I've done a lot of things, all Dev related but ultimately most of my career was spent working on platforms for consumer products. After many attempts I've decided the path forward is to focus on building something that solves my own problem. Micro Chat is a solution to some of the social media problems I've been having.

What I've been looking for most of my life is a community. A place to belong. I scoured the internet for that with strangers. But I think that's wrong. The public forums are also the wrong place to find that connection. What we need to do is focus on smaller communities starting with real connections. We need to strip away a lot of the addictive behaviours and issues created by social media. I think things like hackernews are great because it's very simple text based, with no notification and centers around conversations about topics of interest. I think that's how group chat should also be. The difference here is, I want a place to build small private communities e.g micro communities. Most real groups lose their value beyond a certain size. For me that's around 20 people. As an introvert I really care about strong connections with a handful of people. Unfortunately those real world connections are now spread globally as people moved away and while we have private slacks or WhatsApp grojps to stay in touch it just feels like the wrong setup for that. If anything I want to consolidate it into one place.

Anyway I'm sharing this now to get some feedback. I think the tech and the product will evolve but only by finding out if others feel the same.

https://micro.mu

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.

What if any is the relationship between https://m3o.com/ and https://micro.dev/ ?

I shared this post in a few developer communities like Hacker News and it was well received. Over the past few years I've been working on an open source project called Micro, an API first development platform and I'm now sharing Micro Services, a catalog of reusable real world Micro services.

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.

Wait, I've seen this repository on HN a few days ago: https://github.com/micro/micro

Are you affiliated with this repository? How is it related to yours?

So, I searched for some options, which I found through microservices.io, and saw Go kit and Micro.

There is one project that I know that might fits your interest https://github.com/micro/micro

In our example, requestWork just returns an error parameter. If you need to return multiple parameters, we need to pay attention to data race, which can be solved by mutex. For specific implementation, please refer to go-zero/zrpc/internal/serverinterceptors/timeoutinterceptor.go, I won’t go deep into the details here.

The specific Kubernetes configuration file can be found here, where namespace is modified as needed.

tal-tech/go-zero (Go): go-zero is a web and rpc framework written in Go. It's born to ensure the stability of the busy sites with resilient design. Builtin goctl greatly improves the development productivity.