Live data from Hacker News

New setup for 2020

changelog.com

51–58 of 58 posts

Re: New setup for 2020

#51

Earlier quoted context omitted.

Yes, it does make sense to move static files to object storage, especially the mp3s. There is some ffmpeg-related refactoring that we need to do before we can do this though, and it's not a quick & easy task, so we have been deferring it since it's not that high priority, and there are simpler solutions to this particular problem (i.e. improved CDN caching). Other static files such as css, js, txt make sense to remai…

Yea the small static files that are part of your webapp can stay with it, but media files are best on S3. If you need a block interface though, I recommend something like ObjectiveFS: https://objectivefs.com/ If you're using an operator then local volumes is a good middleground if it automates the replication already. CockroachDB also has a kubernetes operator although it's only for GKE currently. There are also othe…

I've never heard of ObjectiveFS, thanks for the share! I am more inclined to try out Rook, OpenEBS or Longhorn as open source alternatives.

I've just added YugabyteDB to my explore list.

Re: New setup for 2020

#52
post #46

I browsed the site swiftly. Isn't it a bunch of content items, like WordPress site? So, here we are, deploying WordPress in the cloud via Kubernetes, for real, not as a funny meme?

changelog.com used to be WordPress, then became a Phoenix app because it needed features that were hacky to implement & then manage in WP. It's more of a podcasting platform these days rather than a CMS.

The code in this repo tells the truth about what it is, and even shows how it works: https://github.com/thechangelog/changelog.com

Re: New setup for 2020

#53

I'd be interested in learning more about the move from Concourse to Circle (I'm a notorious Concourse fanboy). What went well, what didn't, what you miss, what prompted it -- that sort of thing.

The primary reason behind the move was not wanting to manage CI. Since there were no options for a managed Concourse in 2018, we migrated to Circle, one of the Changelog sponsors at the time. Concourse worked well for us, we didn't have any issues that were being enough to remember. You may be interested in this screenshot that captured the changelog.com pipeline from 2017: https://pipeline.gerhard.io/images/small-os…

Thanks, a very comprehensive answer. I agree especially that the lack of a hosted option has hamstrung Concourse's success.

I couldn't use the Circle CI links, they're auth gated.

Re: New setup for 2020

#54

>>> We no longer provision load balancers, or configure DNS; we simply describe the resources that we need, and Kubernetes makes it happen. This is (part) of what keeps me in the stone age. You are provisioning load balancers and DNS - but just one step removed through k8s And my prior is that we need to understand that, be aaare of it, have a model of what is going on to help develop and debug. And so it feels a bit…

> And my prior is that we need to understand that, be aaare of it, have a model of what is going on to help develop and debug. If it's a sufficiently robust abstraction, you don't, you just learn the abstraction. Kubernetes has reached that point for many folks. I no longer have a detailed mental model of how my compiler or LLVM works, I just trust that it does. When was the last time you needed to (or were capable o…

The car issue is tempting as an argument clincher. My problem is the army - a lot of their trucks and so forth are not computer controlled this-generation-of-toyota-abstraction but have stayed inefficient but repairable trucks. Because they both need to have trucks that are repairable and also all the computer understands is nice paved roads. Which is what armies don't do.

But yes, mostly I am not an army.

Re: New setup for 2020

#55
post #42

>>> We no longer provision load balancers, or configure DNS; we simply describe the resources that we need, and Kubernetes makes it happen. This is (part) of what keeps me in the stone age. You are provisioning load balancers and DNS - but just one step removed through k8s And my prior is that we need to understand that, be aaare of it, have a model of what is going on to help develop and debug. And so it feels a bit…

Let's turn the knobs on the scenario and see how it appears: >>> >>> with the advent of the first programming languages you no longer had to think in terms of registers, loading operands from memory, storing the results back, spilling registers to the stack. >>> You _are_ handling registers and memory spills, but just one step removed through the use of C. The analogy may not be perfect, but I think it makes obvious…

But i think this is apples and oranges - C maps pointers and memory allocation in a very direct robust manner, even Python allows you to dis back to see the stack.

But this hard-line-to-underlying reality is unlikely to exist looking at how this months k8s will configure last years AWS route53.

It just works 80% of the time is a disaster, 98% of the time might be bearable. is it above 99%?

Re: New setup for 2020

#56

It seemed interesting and I tried to subscribe but the process doesn't work without disabling ublock/adblock. I am okay with that so I disabled it but then I failed two captchas round (find bikes in thumbnails, some thumbnails are upside down ?!) :(.

Sorry for the hassle! We’ve been hit by lots of spammers lately so I battened down the hatches. Unfortunately this has the side effect of also blocking some legit humans as well. :(

Could 2FA or a mobile number be a good/practical alternative ?

Re: New setup for 2020

#57
post #42

Earlier quoted context omitted.

Let's turn the knobs on the scenario and see how it appears: >>> >>> with the advent of the first programming languages you no longer had to think in terms of registers, loading operands from memory, storing the results back, spilling registers to the stack. >>> You _are_ handling registers and memory spills, but just one step removed through the use of C. The analogy may not be perfect, but I think it makes obvious…

But i think this is apples and oranges - C maps pointers and memory allocation in a very direct robust manner, even Python allows you to dis back to see the stack. But this hard-line-to-underlying reality is unlikely to exist looking at how this months k8s will configure last years AWS route53. It just works 80% of the time is a disaster, 98% of the time might be bearable. is it above 99%?

Indeed, my point was that it's a quantitative question not a qualitative one.

When compilers created buggy code every other day, when memory allocators were unreliable because memory fragmentation would make it likely for new allocations to fail in the lifetime of a normal program execution, etc, it would be, as you said "a disaster if it works Did k8s reach 99%? The jury is still out. Probably not yet, but in principle I don't see anything wrong pursuing that path just because it's "another layer". We use abstraction layers all the time; they allowed progress (Yes often we went too far)

Re: New setup for 2020

#58

Earlier quoted context omitted.

> And my prior is that we need to understand that, be aaare of it, have a model of what is going on to help develop and debug. If it's a sufficiently robust abstraction, you don't, you just learn the abstraction. Kubernetes has reached that point for many folks. I no longer have a detailed mental model of how my compiler or LLVM works, I just trust that it does. When was the last time you needed to (or were capable o…

The car issue is tempting as an argument clincher. My problem is the army - a lot of their trucks and so forth are not computer controlled this-generation-of-toyota-abstraction but have stayed inefficient but repairable trucks. Because they both need to have trucks that are repairable and also all the computer understands is nice paved roads. Which is what armies don't do. But yes, mostly I am not an army.

computer being tuned for nice paved roads is not really the problem. If the army needed they have the money to put into developing a car computer specialized in whatever terrain they needed to.

Their problem is being easy to repair.

Most of the regular people can take their cars to a shop that will have the really basic in stock (ie. oils and filters) and can order most of the rest from a distributor to have delivered same or next day for most cars. You will only take longer to get specialized parts or parts for unusual cars. Also most people can work around not having a car for a few days even if it is a hassle.

While army base does have specialized mechanics to properly fix the trucks, if one break in the middle of a mission after engagement the team in that truck need to be able to patch it up and get it going on the field.

So the army need trucks that people that are primarily soldiers and not mechanics can patch up "easily" in the field without tons of specialized training, without access to special or weird tools and minimal to no access to parts.

Post reply on HN