Unsafe Operations: Terminology, Hazards, and the End Result
This article explores some of the user interface choices that could be made to emphasize that certain operations are unusual and prevent unintended usage.
Join the DZone community and get the full member experience.Join For Free
dave had an interesting comment about the previous post in this topic.
actually i would have kept the original terms. clarity is way more important than 'protecting' a click-and-point administrator. if an administrator is so incredibly stupid to experiment with an production cluster, then it is his right!
to protect against accidental hits on the very big 'leave cluster' button, you can ask the admin to enter a 3 digit number that is displayed to confirm the action. but leaving and joining a cluster are de facto industry terms which makes it easier for admins coming from other data storage solutions to get a handle on ravendb.
i think that there is some confusion regarding the actual terms. here is the current ui, after the changes i discussed in the previous post:
as you can see, we have “add another server to cluster,” and “leave cluster,” which are standard and common operations, they are what you’ll use in pretty much all cases.
the advanced cluster operations are unsafe , they are there to enable the operator to recover from a disaster that took the majority of the cluster down. those aren’t standard operations, they are hidden by default under “advanced,” and even then we want to make sure that users are thinking about them.
Published at DZone with permission of Oren Eini, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.