We actually do have a coffee-related server that we've open sourced at Etsy: https://github.com/morria/CoffeeD/
I currently have an open (internal to Etsy) bug on the author on making it RFC 2324 compliant.
HN user
We actually do have a coffee-related server that we've open sourced at Etsy: https://github.com/morria/CoffeeD/
I currently have an open (internal to Etsy) bug on the author on making it RFC 2324 compliant.
Just getting to this now, but there's a slight misquote in Fred's post. :) I (and I think Kellan said it at the same time) said "...we don't roll back, we roll forward..."
We do that because it's simply faster and easier to roll forward than to roll back the entire deploy. Rolling forward means taking advantage of the percentage rampups of new code paths, feature and config flags to turn things off/on, and even reverting the 5 line change is simpler than rolling it all back.
So no, I'm not suggesting we let bugs in prod languish while they are debugged for a long while.