3,113 karma · joined June 3, 2011
[ my public key: https://keybase.io/gtaylor; my proof: https://keybase.io/gtaylor/sigs/RO51m-c-5zNyMZc-eSuzjUFw4avULk8Ft20Zz-cj-zA ]
* This is a multi-region (us-east1, us-central1, europe-west1, asia-northeast1 and asia-east1) outage (yeesh)
* Incident began at Incident began at 2017-08-29 18:35 PDT. At the time of this comment, we're over 13 hours (??)
Correct?
There are great companies all around the world, and there are crap companies all over the world.
You can dodge much of the operational complexity in standing a cluster up by starting with Google Container Engine or a provisioner like kops. Once you have enough comfort, you can get more fancy and build something more customized to your cases.
IMO, there are limitless other things I'd rather be doing than these!
Fastly was on top of it and routed around the issue quickly.
> You don't solve a DDoS problem by having less capacity than your attacker and most individual companies can never afford the amount of bandwidth that is at Cloudflare's disposal.
You can have less capacity than Akamai (many excellent providers have less) and still serve this purpose.
Having done this when I was younger and more foolish, I would not recommend it at all. I felt like I did pretty well overall, but ultimately flubbed a couple of [simple] questions that torpedoed my chances. While things worked out for the best (that company's future looks grim and I'm very happy where I am now), it was a blow to my confidence at the time.
I probably wouldn't have had to have prepared for a month or two to get that offer. A week of glancing at my notes for 30 minutes to an hour a day to refresh would have been sufficient. I think you owe it to yourself and the company who is paying to fly you out to at least brush up a _little_ bit (within reason) beforehand. It's almost like basic hygiene.
This is the case for many life decisions. I don't see how this is a helpful addition to the conversation.
* Move to another state? There will be big life implications.
* Change careers? Ditto.
* Go to college?
* Go _back_ to school?
* Spend loads of free time hacking away instead of getting out of the house?
* Travel a bunch, perhaps at the cost of rapid career advancement?
* Take a huge pay cut to work on something you enjoy?
All of these (and more) will limit you in various ways, but gift you with different experiences. The same is for kids.
It sounds like you don't want kids. That's cool, I'm glad you know what you want. But no need to hype up this decision to have kids or not as scary or some kind of albatross. It's just another decision with pros and cons.
On a more general note: It's got to be incredibly hard to do what GitLab does with their extreme transparency. I feel like we have to be careful about reading too deeply into things and nitpicking their culture or process. HN is full of "expert" advice, much of it being terrible. They weighed their options, invited feedback, then made a decision.
I appreciate what GitLab does in being so transparent. None of us are owed explanations or insight into how they operate, yet they go out of their way to provide it. Kudos to syste and his team!
There will be some instances that you'll run 24/7, but this shouldn't be the case for your entire fleet if you're on AWS.
There's just not a ton of substantiated content here. It's mostly really lousy anecdata like:
> Sadly, I am not aware of any serious companies than run on Ubuntu.
I am troubled by the direction of Docker and there are serious issues, some of which were raised in this post. However, whatever signal there is in this post is lost in a sea of noisy ranting.
My advice to anyone who doesn't already have strong opinions:
* Complement any reading that you do with your own research.
* Don't try to invent your own container orchestration system.
* If you aren't sure how to best do something, ask someone!
And for the love of everything holy:
* Don't run stateful systems on Docker if you can't handle failure or data loss!
Docker and orchestration systems like Kubernetes can be an excellent pairing. It's going to require research, a change in how you develop, build, test, and deploy systems, and a gradual building of operational experience. It will not be a quick process, and it's not for every org. But for some orgs and usage cases, it's an excellent way to go!
I was very happy to see YC do their part in what will be a 4-8 year (at least) battle of attrition and will. The ACLU is one of the best advocates for the people, in a country where corporate and religious lobbying trumps most.
Alternatively, all Jobs matching this query must succeed before this job. Failures can be OK if a configurable threshold of success is met. Exceeding the thresh fails the dependent jobs before they get to run.
You can do all of this with supervisor pods, but since you asked...