Re:Keystone Interface
by vajrabum on Thursday April 30, 2020 @11:05AM
(#23031610)
It seems kind of weird that the article doesn't mention feature flags since they solve pretty much the same problem and Fowler first wrote about feature flags as long ago as 2010. Both solutions avoid feature branches. Feature flags create a small amount of tech debt since the code will need to be removed post GA, but allow end to end tests and staged rollouts over a long period of time which the keystone interface does not.
[ Parent
| on HN ]
I found the same thing odd too, but in the back of my mind I was thinking that the idea was "have the feature flag control only the UI; all else is live from the get go and run through CI etc".
The idea of the feature flag could be expanded too, so that if "off" it generated some dummy data while when "on" had the data come from the now-visible UI field.
Re:Keystone Interface
by DerpyBaby123 on Thursday April 30, 2020 @11:57AM
(#23032263)
It does mention them, using the synonymous term Feature Toggle
>That said, there are cases when the UI can't be packaged into a simple keystone. When that's the case then it's time to use Feature Toggles.