221–230 of 277 posts
Isnt this a wrapper script over VirtualBox?? Whats the value?!
But Hashicorp has a lot of tools which make sense as building-blocks in a software architecture or in CI/CD pipelines.
Most of the tools I would put in the DevOps space, so they enable people to build, deploy and release more consistently.
My thoughts not facts. I know that there are more products then I mention. I fail to see in what segment Hashicorp will remain relevant over time. Terraform is the tool I mostly see companies pay for. Over time cloud vendors will make Terraform obsolete. In fact it is already a problem to use Terraform since it can not move at the same pace as major cloud vendors. Vault is an extremely complicated niche tool, most co…
I feel I need to reply with my thoughts. - Vault is not niche - it’s THE way to manage pki and credentials if you’re half serious about security. Which is why you’re now are starting to see managed vault. - Consul - EVERYONE should use service discovery, cloud or not. It’s indispensable for numerous reasons. If you doubt it’s relevance, check out the Kubernetes integration work - there’s a reason for that focus. You…
Earlier quoted context omitted.
I feel I need to reply with my thoughts. - Vault is not niche - it’s THE way to manage pki and credentials if you’re half serious about security. Which is why you’re now are starting to see managed vault. - Consul - EVERYONE should use service discovery, cloud or not. It’s indispensable for numerous reasons. If you doubt it’s relevance, check out the Kubernetes integration work - there’s a reason for that focus. You…
> Consul - EVERYONE should use service discovery, cloud or not. Discovery means that you don’t know your service name? Or endpoints? How can one lose his service? Im def missing something :)
Earlier quoted context omitted.
I really don´t feel K8S have won this battle. I agree people talk more about K8S but i have seen a trend in people that are disappointed with K8S and move against Nomad instead. I guess K8S is too messy. It´s like taking a 2015 enterprise vsphere datacenter environment and containerizing it. Too many layers.. But of course, there´s no fully managed Hashicorp offer for all products in GCP or AWS, Azure....
I do not really understand why people run so many things in containers in the first place. Sure, for sand-boxing and sometimes resource utilization, but the large services I worked on have always been on 10+ dedicated high-end servers with 200GB+ memory each. Absolutely zero need for any additional abstractions. You can also design solutions that use a lot of memory in contrast to containers.
Earlier quoted context omitted.
True. The number of engineers is not linearly correlated with the number of customers, but the number of features. If you have a relatively simple product and you can somehow still compete (niche market, patents etc), you can get away with a very low head count. WhatsApp famously had only 35 engineers and ~450M users when Facebook acquired them.
If they wanted, they can expand easily to a lot more - which is probably what happened to them inside facebook anyways. Even then, they can still be insanely profitable per engineer.
I think initially they only expanded to ~50 engineers until 900M users. Even today they are estimated to have only ~500 employees (no idea what percentage of that are engineers).
Earlier quoted context omitted.
One might argue that those are costs, not head count. By the same logic we can also assume that they use contractors who bake pizzas for Facebook employees when they order from Domino's. I guess a somewhat better metric would be "profit per employee" instead of revenue.
"contractors who bake pizzas for Facebook employees when they order from Domino's" Clearly keeping facebook platform from breaking the law on childporn is pretty central to their business, but pizza is not
Earlier quoted context omitted.
Jap, I bet it’s related to this chart https://fred.stlouisfed.org/series/M1NS
You might want to read that footnote about the definition of M1 changing at May 2020
A high amount of money was printed in that exact timeframe though.
What’s a good graph to show that?
Earlier quoted context omitted.
I feel I need to reply with my thoughts. - Vault is not niche - it’s THE way to manage pki and credentials if you’re half serious about security. Which is why you’re now are starting to see managed vault. - Consul - EVERYONE should use service discovery, cloud or not. It’s indispensable for numerous reasons. If you doubt it’s relevance, check out the Kubernetes integration work - there’s a reason for that focus. You…
> Consul - EVERYONE should use service discovery, cloud or not. Discovery means that you don’t know your service name? Or endpoints? How can one lose his service? Im def missing something :)
Earlier quoted context omitted.
I feel I need to reply with my thoughts. - Vault is not niche - it’s THE way to manage pki and credentials if you’re half serious about security. Which is why you’re now are starting to see managed vault. - Consul - EVERYONE should use service discovery, cloud or not. It’s indispensable for numerous reasons. If you doubt it’s relevance, check out the Kubernetes integration work - there’s a reason for that focus. You…
Could you elaborate on the service discovery part? If you're in kubernetes, you have kube-dns which in effect is service discovery right? What does consul provide over this?
I’ve yet to set foot in a bigger place with distributed teams and services that only use k8s and nothing else.
In these settings there’s a need to interconnect and monitor everything.
I’ve even at one time registered mainframe stuff in consul, as an external service, with a rather complex health checks in place. This alone improved observability and reliability for a lot of the distributed consumers.
Holly mother of God. Mitchell was still on HN yesterday, as he was replying something about Backblaze IPO and its business. Today it is his IPO, $259 million revenue. 2100+ Customers, 1500+ employees, $10 Billion Valuation......... I mean I felt it wasn't that long ago Vagrant was "the" tool for the job. How it all started, the submission on HN [1], quote: > This project has been the love child of myself and John Ben…
> 1500+ employees According to LinkedIn the average tenure of employees is a little over a year (likely to hit the vesting cliff and bounce). Two months ago they didn't have the staff to review pull requests: https://news.ycombinator.com/item?id=28425849 You can love the product, but investors are ultimately betting on the company - which seems shaky.