Micro

Dev tools

microservice toolkit

SHOW HN2016

101points
32comments
#370of 2,264 in 2016
Top 17%of 2016 by points

How HN took it

MixedNo clear lean

3 positive, 5 neutral or asking, 0 mixed, 6 critical, out of 14 comments about the project. Thread score -0.25.

Idea: 1 for, 4 againstDocs: 0 for, 1 againstDesign: 1 for, 0 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Sidecar approach with RPC, pubsub, reverse proxy and registry looks sharp

    From 1 comment
    • Although 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 /…
      brightball on HN

Objections

  • Microservices add heavy client-side complexity for discovery, retries and timeouts

    From 2 comments
    • More 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…
      agentgt on HN
    • Your observation about clients requiring more and more logic (e.g. discovery, reconnecting, timeout, etc) is spot on. It is a pretty big overhead and teams that are building an…
      lifty on HN
  • Toolkit ignores transactions across services

    From 1 comment
    • It's great that more and more toolkits are being released. But my biggest gripe with Microservice architectures and toolkits are that they ignore transactions across services.
      saintfiends on HN
  • Microservices are a poor fit for uprooting existing architecture

    From 1 comment
    • microservice is a horrible horrible idea to uproot your existing architecture or build on top of.
      jorgecurio on HN

Requests

  • Clarify how Micro differs from go-kit

    From 1 comment
    • 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…
      geoka9 on HN

Questions

  • Is it fault tolerant and does it support hot swapping?

    From 1 comment
  • Why create Micro instead of contributing to go-kit?

    From 1 comment
    • Why did you decide to create micro and go-platform instead of contributing to go-kit (https://github.com/go-kit/kit)?
      tonyhb on HN

Alternatives named

  • linkerd

    From 1 comment
    • You may be interested in linkerd (https://linkerd.io) -- we built it specifically to address the complexity of proper connection management at scale (service discovery, timeouts,…
      williamallthing on HN
  • go-kit

    From 1 comment
    • Why did you decide to create micro and go-platform instead of contributing to go-kit (https://github.com/go-kit/kit)?
      tonyhb on HN
  • SmartStack and Kafka

    From 1 comment
    • The sidecar part of this looks like what is essentially SmartStack[1] but requiring the user be aware of it's existence (due to Micro's proto3 api) whereby users of SS can more…
      crazy_geek on HN
  • Mantl

    From 1 comment
    • I want to second the fact that a microservice architecture is great because of the ease of deployments (but only after the initial overhead!). I can attest first-hand to the…
      spudfkc on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/11327679)