4 ms·

Totally not, I'm working in Poland. And, I'm sorry to say, if you haven't heard about Consul, then you're really not in a position to judge if infrastructure to

Totally not, I'm working in Poland. And, I'm sorry to say, if you haven't heard about Consul, then you're really not in a position to judge if infrastructure tools are or aren't written in Go. Consul is the de'facto industry standard for service discovery for a few years already. EDIT: Cockroach is actually the most SV'ish of all those.

kuschku 10y ago
> Consul is the de'facto industry standard for service discovery for a few years already. So standard that it doesn’t even have a Wikipedia page? Nor is there even one for this specific type of datacenter-oriented service discovery? This is all pretty niche tech, used by a handful of startups that engineer technology for billions of users, but not used anywhere else. I’ve never seen any companies on national scale operate with this – nor would they need to.
- cube2222 10y ago
  The thing is, I know a lot of companies using it at nationwide scale (non-startups). I think there's a reason you are getting downvoted. Anyways, Service Discovery like this is less niche than containers are. If containers are still niche for you, then there you go.
  - kuschku 10y ago
    > I think there's a reason you are getting downvoted. Well, so are you, your comments are even so grey I can barely read them anymore (and I can’t downvote you). Regarding the rest: Containers are far less niche than Consul is. For service discovery, the market isn’t nearly as monopolized as containers are. And containers are far more used than consul is – most places I’ve seen build their own service discovery systems, or hardcode a main node and then have services in containers register with that, etc. While for containers, at the moment, there’s almost only docker, due to the ecosystem.
maloney 10y ago
etcd is also used quite a bit for service discovery, but it's written in Go too :)
- cube2222 10y ago
  Are you using it personally? I never met anyone using it for that. How's your experience with it been? (in case you did use it)
unscaled 10y ago
I think you exaggerate. Consul is probably the go-to discovery service discovery for new projects at startups and tech companies that aren't afraid of the bleeding edge, but if you count installed base and less bleeding-edge companies ZooKeeper probably still reigns supreme.
- kuschku 10y ago
  Definitely. And while ZooKeeper is common, (and apparently Consul is now the hot new thing, I guess?), many places also build their own systems. I wouldn’t call Consul "industry-dominating technology", as you’d do with ElasticSearch, Hadoop, Spark, etc.
  - cube2222 10y ago
    I'd call Spark a much more bleeding edge product than Consul. And no, it's not the hot new thing at all. It's just a standard tool.
  - unscaled 10y ago
    And the funny part is that all of them are Java. :) Well, except Spark which is Scala.
    - kuschku 10y ago
      Yes, exactly. In a list of most important tools out there, Go only turns up for a few tasks that used to be done in C++, as layer between the OS and services. Almost everywhere else, it’s not "industry-dominating" at all, so I’m not sure why people use the argument "go is used everywhere and everything is in go" (which is obviously false) to argue that go is a good language. (besides, C is actually used everywhere, but no one would use that as argument to show how C is a good language).

kuschku 10y ago

> Consul is the de'facto industry standard for service discovery for a few years already. So standard that it doesn’t even have a Wikipedia page? Nor is there even one for this specific type of datacenter-oriented service discovery? This is all pretty niche tech, used by a handful of startups that engineer technology for billions of users, but not used anywhere else. I’ve never seen any companies on national scale operate with this – nor would they need to.

cube2222 10y ago
The thing is, I know a lot of companies using it at nationwide scale (non-startups). I think there's a reason you are getting downvoted. Anyways, Service Discovery like this is less niche than containers are. If containers are still niche for you, then there you go.
- kuschku 10y ago
  > I think there's a reason you are getting downvoted. Well, so are you, your comments are even so grey I can barely read them anymore (and I can’t downvote you). Regarding the rest: Containers are far less niche than Consul is. For service discovery, the market isn’t nearly as monopolized as containers are. And containers are far more used than consul is – most places I’ve seen build their own service discovery systems, or hardcode a main node and then have services in containers register with that, etc. While for containers, at the moment, there’s almost only docker, due to the ecosystem.

maloney 10y ago

etcd is also used quite a bit for service discovery, but it's written in Go too :)

cube2222 10y ago
Are you using it personally? I never met anyone using it for that. How's your experience with it been? (in case you did use it)

unscaled 10y ago

I think you exaggerate. Consul is probably the go-to discovery service discovery for new projects at startups and tech companies that aren't afraid of the bleeding edge, but if you count installed base and less bleeding-edge companies ZooKeeper probably still reigns supreme.

kuschku 10y ago
Definitely. And while ZooKeeper is common, (and apparently Consul is now the hot new thing, I guess?), many places also build their own systems. I wouldn’t call Consul "industry-dominating technology", as you’d do with ElasticSearch, Hadoop, Spark, etc.
- cube2222 10y ago
  I'd call Spark a much more bleeding edge product than Consul. And no, it's not the hot new thing at all. It's just a standard tool.
- unscaled 10y ago
  And the funny part is that all of them are Java. :) Well, except Spark which is Scala.
  - kuschku 10y ago
    Yes, exactly. In a list of most important tools out there, Go only turns up for a few tasks that used to be done in C++, as layer between the OS and services. Almost everywhere else, it’s not "industry-dominating" at all, so I’m not sure why people use the argument "go is used everywhere and everything is in go" (which is obviously false) to argue that go is a good language. (besides, C is actually used everywhere, but no one would use that as argument to show how C is a good language).