Reliability: It’s not great

(community.fly.io)

1226 points bishopsmother | 3 comments | 06 Mar 23 17:47 UTC | HN request time: 0.656s | source

Show context

emschwartz ◴[06 Mar 23 18:53 UTC] No.35045790[source]▶

>>35044516 (OP) #

One of my colleagues keeps repeating “reliability is our number one feature”.

I’m not sure it is for 100% of early stage startups, but I guess it is once you exceed some minimum usage threshold.

That said, definitely appreciate the detailed explanation.

replies(4): >>35046668 #>>35046901 #>>35047002 #>>35053993 #

1. jpdb ◴[06 Mar 23 19:52 UTC] No.35046668[source]▶

>>35045790 #

> One of my colleagues keeps repeating “reliability is our number one feature”.

I think reliability is the #1 feature at any stage because if you're unavailable, you're at best useless and more than likely you are actively harmful because your users have an expectation.

However, if you're unavailable outside of times customers don't expect you to be there then you're not actually unavailable. This is more likely for an early stage start-up, but you don't typically choose or know when you're expected to be available nor do you always get to choose when you're unavailable.

replies(2): >>35046932 #>>35047797 #

2. sa46 ◴[06 Mar 23 20:13 UTC] No.35046932[source]▶

>>35046668 (TP) #

In terms of confidentiality, availability, and integrity: I'll bet LastPass would gladly trade availability right now to regain confidentiality.

3. ignoramous ◴[06 Mar 23 21:22 UTC] No.35047797[source]▶

>>35046668 (TP) #

Our team at AWS had a poster up on the wall that more or less went:

1. Security

2. Durability

3. Availability

4. Speed

↑