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

How we built JSR

deno.com

Post reply on HN
Print view View original

11–20 of 41 posts

Re: How we built JSR

#11

Post by lionkor »

I'm not sure what 100% uptime is supposed to mean. Zero downtime, thats like saying zero bugs - it's not going to happen. Even 99.9999% uptime would be realistic, but 100% is not happening. There are factors out of your control that you cant guarantee will not even be down 1ms per year.

How do you manage 100% uptime when your db is only going to be 99.9%? The latter is almost easy, the former, even if we assume 99.99999%, really really hard.

Just silly and may show that there are some unrealistic assumptions, maybe? Or maybe the team doesn't know much about reliability -- also concerning.

Just target six nines and be done with it, or something.

In may of last year, NPM was down to 99.8 for the month.

Re: How we built JSR

#12

Post by paxys »

lionkor wrote: post #11

I'm not sure what 100% uptime is supposed to mean. Zero downtime, thats like saying zero bugs - it's not going to happen. Even 99.9999% uptime would be realistic, but 100% is not happening. There are factors out of your control that you cant guarantee will not even be down 1ms per year. How do you manage 100% uptime when your db is only going to be 99.9%? The latter is almost easy, the former, even if we assume 99.99…

It's a goal, not a guarantee.

Re: How we built JSR

#13

Post by danpalmer »

> So how do we make serving modules reliable? We defer the entire problem to Google Cloud. The same infrastructure that serves google.com and YouTube is used to host modules on JSR. None of our custom code sits in this hot path

I work at Google and even I do this. Services like the storage backing GCS are incredibly reliable and have teams of SREs supporting them, so I offload as much as possible to services that have more dedicated support than I'm able to provide.

Re: How we built JSR

#16

Post by Thaxll »

Just a small point but google.com and YouTube do not run on the same infra as what you see on GCP, especially if you use GKE etc...

It's trivial to see because when GCP is down somehow Google and Gmail keep working.

Re: How we built JSR

#17

Post by lionkor »

paxys wrote: post #12
lionkor wrote: post #11

I'm not sure what 100% uptime is supposed to mean. Zero downtime, thats like saying zero bugs - it's not going to happen. Even 99.9999% uptime would be realistic, but 100% is not happening. There are factors out of your control that you cant guarantee will not even be down 1ms per year. How do you manage 100% uptime when your db is only going to be 99.9%? The latter is almost easy, the former, even if we assume 99.99…

It's a goal, not a guarantee.

Yes, but it means nothing. If the realistic version of that goal is 99.99%, thats not very good at all.

You wouldnt applaud me if I said my goal total comp was 1M, and then i went and got a job that pays 30k.

Re: How we built JSR

#19

Post by segfaultbuserr »

mike256 wrote: post #4

Why JSR (Java Specification Request)?

Jump to Sub-Routine?

6800: http://www.8bit-era.cz/6800.html

6502: http://www.6502.org/tutorials/6502opcodes.html#JSR

PDP-11: https://programmer209.wordpress.com/2011/08/03/the-pdp-11-as...

Motorola 68000: https://mrjester.hapisan.com/04_MC68/Sect05Part05/Index.html

Post reply on HN