4 ms·
A good engineer can build a bridge out of rotten trees. But they could still build a better bridge, in less time, with proper materials.
by kuschku 10y ago
A good engineer can build a bridge out of rotten trees.
But they could still build a better bridge, in less time, with proper materials.
- cube2222 10y agoYou know, I think, maybe it's not a coincidence that almost all high-scale infrastructure tooling is written in Go nowadays.
- kuschku 10y agoAlmost all high-scale infrastructure tooling? Are there many databases, parallelism frameworks, indexing systems, or machine learning frameworks in go? I’d be interested if you can name any fields where non-Google go projects dominate. I only know of containers.
- cube2222 10y agoService Discovery and configuration (Consul, etcd), Monitoring (Prometheus and Influx), non-container cluster management (Nomad), databases (CockroachDB), messaging (NATS, Jocko), Terraform. Other than that, I think everybody noticed the frequent posts "xxx database written in Go". Also, most high scale computing companies now use Go for their infrastructure parts. EDIT: You can also check out all the stuff the CoreOS team puts out.
- kuschku 10y agoI’ve actually never used any of them, and none of the devs or ops people I usually talk to used them either. We never even heard of any of those except for CockroachDB. Are you sure these are "dominating the entire industry"-products, as you mentioned before? Or is it more that they’re only used in SV?
- cube2222 10y agoTotally 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 agoThe 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