People who work AT SCALE (tm): Can you think of any situation where backend performance or consistency considerations affected the design of interactions on the front-end in a way that introduced something like a human anti-pattern you eventually discovered well after the fact?
-
-
Had a scenario like this at my prev company. Shopping search engine, saw ~1mil unique users per day, we built a user action threshold where we would store a user's viewed/saved items in a DB only after a certain # of "action points" accumulated (+1 per view, +5 for save, etc)
-
This worked great to save our db cluster from unnecessary writes, cut db load and size by 90% or more, big win! ...until marketing/product management got wind of it and turned it into a "force signups after N actions" feature

- 1 more reply
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.