4 ms·

Hi, author here. I built Micro based on my experience at Google and Hailo. At Hailo we built a global microservices platform with over 200 bespoke services in p

by chuhnk 11y ago

Hi, author here. I built Micro based on my experience at Google and Hailo. At Hailo we built a global microservices platform with over 200 bespoke services in production by the time I left. I realised that more and more people were tackling the problem of scale both technically and as an organisation. I felt like the tools were lacking and most companies end up building their own from scratch. Micro was a way of creating a foundation for writing and running distributed systems. It's a pluggable architecture so that the underlying systems can be swapped out based on preference. Beyond Micro, I'm working on go-platform https://github.com/micro/go-platform https://github.com/micro/go-platform which addresses the higher level needs for microservices. Auth, monitoring, metrics, distributed tracing, etc, etc. Again pluggable like Micro. Still in it's infancy. Cheers Asim

spriggan3 11y ago
Is it fault tolerant ? does it support hot swapping ?
- chuhnk 11y ago
  Fault tolerant in what way? And hot swapping in what way? Go micro uses client side selection and load balancing so you can set number of retries and the timeout period so that it will iterate through nodes for a given request. There's also implementations for rate limiting and circuit breakers as client side wrappers/middleware in the go-plugins repo https://github.com/micro/go-plugins/tree/master/wrapper https://github.com/micro/go-plugins/tree/master/wrapper. Plugins themselves can either be imported and added to a map within the go-micro/cmd package which can be set via flags or env vars or you can set it up yourself and pass it into the client/server. Go does not support DSOs yet so bit difficult to do "hot swapping" in that way if thats what you mean.
tonyhb 11y ago
Why did you decide to create micro and go-platform instead of contributing to go-kit (https://github.com/go-kit/kit https://github.com/go-kit/kit)?
- chuhnk 11y ago
  I just had a different vision for how such a thing would be built based on my experiences and I think the great thing about programming and open source is that we're free to explore our own choices. I'm used to writing software in a certain way based on my accumulative experience and there's certain types of people who also gravitate towards it.
  - geoka9 11y ago
    Could you expand on how micro is different from go-kit and why would somebody choose one over the other? Something for the people who are trying to make a decision without getting their feet wet with both toolkits first.
  - tonyhb 11y ago
    That's really cool. You're right that we have so much freedom to interpret the problems we see and solve them in our own right. Thanks for putting this out there and standing up for your work.
cyber 11y ago
"""Micro was a way of creating a foundation for writing and running distributed systems. It's a pluggable architecture so that the underlying systems can be swapped out based on preference.""" At what point do we just admit that we've re-invented the large co-ordination frameworks of years past? Like CORBA? Is it the point where we add a JSON schema validator? or switch to Protocol Buffers or some variant?
- chuhnk 11y ago
  I think those who've been doing this for a while joke about it all the time. I know I do. I and many others have no illusions about the cyclical nature of technology. It's just that at certain points in time we've tried certain methods and they just weren't the right fit or bastardised to a point of becoming more of a problem. So we try again, lo and behold, we start to get somewhere with it. Moving to a distributed system is inevitable when you want to scale. We make certain tradeoffs doing it. Over the next couple of decades we'll see some cycles happen again where monoliths are cool again and then distributed systems come back into fashion. Just the way it goes.

by chuhnk 11y ago

spriggan3 11y ago

Is it fault tolerant ? does it support hot swapping ?

chuhnk 11y ago
Fault tolerant in what way? And hot swapping in what way? Go micro uses client side selection and load balancing so you can set number of retries and the timeout period so that it will iterate through nodes for a given request. There's also implementations for rate limiting and circuit breakers as client side wrappers/middleware in the go-plugins repo https://github.com/micro/go-plugins/tree/master/wrapper https://github.com/micro/go-plugins/tree/master/wrapper. Plugins themselves can either be imported and added to a map within the go-micro/cmd package which can be set via flags or env vars or you can set it up yourself and pass it into the client/server. Go does not support DSOs yet so bit difficult to do "hot swapping" in that way if thats what you mean.

tonyhb 11y ago

Why did you decide to create micro and go-platform instead of contributing to go-kit (https://github.com/go-kit/kit https://github.com/go-kit/kit)?

chuhnk 11y ago
I just had a different vision for how such a thing would be built based on my experiences and I think the great thing about programming and open source is that we're free to explore our own choices. I'm used to writing software in a certain way based on my accumulative experience and there's certain types of people who also gravitate towards it.
- geoka9 11y ago
  Could you expand on how micro is different from go-kit and why would somebody choose one over the other? Something for the people who are trying to make a decision without getting their feet wet with both toolkits first.
- tonyhb 11y ago
  That's really cool. You're right that we have so much freedom to interpret the problems we see and solve them in our own right. Thanks for putting this out there and standing up for your work.

cyber 11y ago

"""Micro was a way of creating a foundation for writing and running distributed systems. It's a pluggable architecture so that the underlying systems can be swapped out based on preference.""" At what point do we just admit that we've re-invented the large co-ordination frameworks of years past? Like CORBA? Is it the point where we add a JSON schema validator? or switch to Protocol Buffers or some variant?

chuhnk 11y ago
I think those who've been doing this for a while joke about it all the time. I know I do. I and many others have no illusions about the cyclical nature of technology. It's just that at certain points in time we've tried certain methods and they just weren't the right fit or bastardised to a point of becoming more of a problem. So we try again, lo and behold, we start to get somewhere with it. Moving to a distributed system is inevitable when you want to scale. We make certain tradeoffs doing it. Over the next couple of decades we'll see some cycles happen again where monoliths are cool again and then distributed systems come back into fashion. Just the way it goes.