What I mean by this is that security is paramount. In the extreme case, customers would prefer downtime to being exploited/defaced/infiltrated. Durability is similar: accepting a commit you can't stand over is no good. And downtime is the worst kind of slowness.
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
(Cost) Efficiency vs (raw/absolute) cost is another potential system design trade-off to make the top N list.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Definitely represents a point of view. Data Engineering would have a #0 of correctness.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I think the priority order varies with the lifecycle stage of the product and company. Think start up trying to prove an idea vs. giant company with custody of information of lots of customers.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I tend to bucket durability (of commits) under availability (of the service and data). Availability as uptime seems more limiting.
-
Can you explain more? I don't think I understand what you mean by durability of commits being an aspect of availability.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.