GitHub was down

Re:GitHub was down by avaer on Tuesday June 06, 2017 @08:49PM (#14502865)

Sure, if you measure uptime of your business and dev team by whether you're serving pages. I wouldn't.

If Github being down means you're not fixing your site today, I'd call it a runtime dependency.

[ Parent | on HN ]

Re:GitHub was down by mehwoot on Tuesday June 06, 2017 @08:53PM (#14502888)

I kind of see your point but it's the wrong phrase. It's not a runtime dependency in a technical sense.

[ Parent | on HN ]

Re:GitHub was down by mygo on Wednesday June 07, 2017 @01:12AM (#14503902)

see now you're just splitting hairs and getting into philosophy. if your website will be stale tomorrow because you can't update it today, then that is a runtime dependency imo.

[ Parent | on HN ]

Re:GitHub was down by paulddraper on Wednesday June 07, 2017 @01:26PM (#14508188)

Why it is down tomorrow?

(Hint: sans hug of death, because a runtime dependency brought it down.)

[ Parent | on HN ]

Re:GitHub was down by paulddraper on Tuesday June 06, 2017 @10:11PM (#14503195)

Incorrect. You need build-time dependencies to change an application, and runtime dependencies to run it.

Deploying/scaling is somewhere in the middle.

[ Parent | on HN ]

Re:GitHub was down by jonaf on Tuesday June 13, 2017 @11:03AM (#14545280)

Yeah, I should have clarified I was talking with my operations hat on. From a development perspective, you might call it a "deploy-time" or "scale up" dependency.

[ Parent | on HN ]