Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

HashiCorp – S1

sec.gov

Post reply on HN
Print view View original

191–200 of 277 posts

Re: HashiCorp – S1

#191

Post by gorgoiler »

robbedpeter wrote: post #190
Aperocky wrote: post #177

Earlier quoted context omitted.

The economy of scale - at FAANG(MAANG?) scale you can have extremely efficient money making features that only takes a few engineer to support thousands. For things that are completely software, it does not surprise me that millions per employee in earnings is realized - that's just what happens when you operate at that scale. And that's accounting for all of the overhead in personnel that scale entails.

Given recent name changes, MAANG works, but it can be MANGA or MAGNA now. I like "MAGNAM" if you include Microsoft.

Ahem, and the G stands for Alphabet? :)

Re: HashiCorp – S1

#192

Post by baby »

That hashicorp golang code is some of the best code I’ve got to read as a pentester. Looking forward to the IPO.

Re: HashiCorp – S1

#193

Post by da39a3ee »

robbedpeter wrote: post #190
Aperocky wrote: post #177

Earlier quoted context omitted.

The economy of scale - at FAANG(MAANG?) scale you can have extremely efficient money making features that only takes a few engineer to support thousands. For things that are completely software, it does not surprise me that millions per employee in earnings is realized - that's just what happens when you operate at that scale. And that's accounting for all of the overhead in personnel that scale entails.

Given recent name changes, MAANG works, but it can be MANGA or MAGNA now. I like "MAGNAM" if you include Microsoft.

If F => M then doesn't G => A? Which is good, we don't want to have to go around calling them MAGNA!

Re: HashiCorp – S1

#194

Post by sneak »

ksec wrote: post #42

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…

I think it's funny and fitting that his eponymous company made Consul and Vault and his personal website doesn't do TLS.

Bigger fish to fry. I wish I had that level of focus!

Re: HashiCorp – S1

#195

Post by remram »

handrous wrote: post #106
ksec wrote: post #42

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…

> I mean I felt it wasn't that long ago Vagrant was "the" tool for the job. Vagrant is my safety hatch, in case Docker goes under and aspect of it that's "the best centralized, cross-distro, server-oriented Linux package manager repository around" is, at least temporarily, thrown into disarray. Back to picking a distro and contorting it into what I need, in that case. And it's still better than Docker if you're reall…

Vagrant also supports running workloads in Docker containers rather than virtual machines (vagrant up --provider docker)

https://www.vagrantup.com/docs/providers/docker/basics

Re: HashiCorp – S1

#196

Post by remram »

__jem wrote: post #108
handrous wrote: post #106

Earlier quoted context omitted.

> I mean I felt it wasn't that long ago Vagrant was "the" tool for the job. Vagrant is my safety hatch, in case Docker goes under and aspect of it that's "the best centralized, cross-distro, server-oriented Linux package manager repository around" is, at least temporarily, thrown into disarray. Back to picking a distro and contorting it into what I need, in that case. And it's still better than Docker if you're reall…

Docker at this point is just a wrapper around OCI spec… why would you go back to Vagrant rather than just using any of the other tools that can build OCI images? Vagrant and Docker seem like fundamentally different tools to me.

Vagrant can use containers, making it also a wrapper around OCI-compatible runtimes. In addition, it also supports VirtualBox, Hyper-V, VMWare, bare metal, SSH targets, and various cloud providers.

The real conclusion from your logic would be: why would you go to Docker rather than just using Vagrant?

Re: HashiCorp – S1

#197

Post by yellow_lead »

N00bN00b wrote: post #178
yellow_lead wrote: post #37

Earlier quoted context omitted.

You might want to read that footnote about the definition of M1 changing at May 2020

Just odd. Why would you change a definition in the middle of an existing chart... Just call it M1a or M11 and add a new chart. Curious what is really going on that I'm not supposed to understand.

Yeah, because the end result is people pointing to it as though it's some extraordinary change. My guess would be it was easier and they're lazy bureaucracy.

Re: HashiCorp – S1

#199

Post by stevekemp »

nuker wrote: post #185
nodesocket wrote: post #147

Earlier quoted context omitted.

You are missing the point. They are the de-facto standard in DevOps tooling from one person startups to gigantic public tech FAANG companies. My prediction, HashiCorp after IPO'ing will get acquired.

> They are the de-facto standard in DevOps tooling Im in cloud automation 8+ years. No they are not de-facto standard. For AWS projects, I much prefer Cloudformation. App devs use venv or similar, not Vagrant. I’d use their CI/CD if they had one, like GitLab, but looks like they don’t?

I've used terraform in 50% of my jobs over recent years.

But even in the companies where I've used AWS and cloudformation we still use Hashicorp tooling. For example we use cloudformation at the current company to handle our AWS infrastructure, but the AMIs launched are generated with packer.

Re: HashiCorp – S1

#200

Post by fragmede »

AtNightWeCode wrote: post #105
jordanbeiber wrote: post #92

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…

All major clouds have better alternatives to Vault. Vault is mostly for really large companies that want to run things like this by themself. There is no need for service discovery in the cloud in general. I have also used Nomad a lot. Maybe it is because we always needed the cutting edge features in general, but in general not very good quality. Core features always worked though. People should use Kubernetes instea…

> There is no need for service discovery in the cloud in general.

That's an interesting take! How do you route requests to the right VM/instance whilst VMs go up/down?

Post reply on HN