Show HN: Micro – a microservice toolkit
blog.micro.mu
Show HN: Micro – a microservice toolkit
1–10 of 33 posts
Re: Show HN: Micro – a microservice toolkit
#2> By now you may have heard of this new phenomenon, microservices.
This reads like a joke... but reading on I don't understand if you meant it...
Re: Show HN: Micro – a microservice toolkit
#3Although having another microservice toolkit for Go won't generate many headlines, the Sidecar approach they've described here does look pretty sharp.
The combination RPC / Pubsub / Reverse Proxy + registry is pretty sharp.
Re: Show HN: Micro – a microservice toolkit
#4github.com/micro/micro is this canonical import name? Serious Go projects usually have serious canonical import name. Examples,
- golang.org/x/net/html/charset
- google.golang.org/cloud
- camlistore.org/pkg/app
- willnorris.com/go/imageproxy
Re: Show HN: Micro – a microservice toolkit
#5Kind of off topic but does anyone know which blog platform / theme this is? Looks like Ghost?
Re: Show HN: Micro – a microservice toolkit
#6Kind of off topic but does anyone know which blog platform / theme this is? Looks like Ghost?
Snooping around in code shows that it is this one: https://github.com/TryGhost/Casper
Re: Show HN: Micro – a microservice toolkit
#7More and more I see toolkits basically turning microservice into a message queue system. More and more intelligent behavior is needed at the endpoints that its starting to leak into the pipes.
Often times the behavior of the endpoints (e.g. discovery, reconnecting, timeout, etc) is so critical that you need that in all clients which totally defeats the "decoupling" of microservices [1] (ie any language or technology can participate). That is extremely complicated endpoint logic requires shared components (see referenced article).
You could get all of the behavior by having a semi smart broker like RabbitMQ with out having an extremly complicated endpoints... but thats not microservice.. its evil old enterprise single point of failure.
Perhaps I'm biased, old school or just so jaded of hearing "microservice" but I really think many companies particularly young startups could get more work done with an intelligent pipe ie message broker over fairly complicated to setup microservies and duplicated intelligent endpoint logic.
TL;DR semi-smart pipes are looking better and better these days.
[1]: http://www.microservices.com/ben-christensen-do-not-build-a-...
Re: Show HN: Micro – a microservice toolkit
#8Hi, 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 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
Re: Show HN: Micro – a microservice toolkit
#9> By now you may have heard of this new phenomenon, microservices. This reads like a joke... but reading on I don't understand if you meant it...
My exact thoughts, as well.
Re: Show HN: Micro – a microservice toolkit
#10> By now you may have heard of this new phenomenon, microservices. This reads like a joke... but reading on I don't understand if you meant it...
It's sattire for sure. Everything has a phase of being a buzzword. Buzzwords annoy the crap out of me but I've also been using the word microservices before it was a thing, back when just Netflix was blogging about it. I could say SOA or distributed systems but I say microservices because it encapsulates what I'm trying to say, "looseley coupled service oriented architecture with a bounded context", Adrian Cockroft's words.