Download as PDF, PPTX
![pen4education
Common practices
• Compiled / hardcoded
users = ['user1', 'user2']
• Command-line arguments
$ java MyApp user1,user2
• Property files
users = user1,user2
• Relational databases
> update user set role='admin' where id=1;
• Key-value stores
> sadd users user1](https://image.slidesharecdn.com/tdc2018featureflagsereleasescontrolados-trilhaxp-180731192533/85/TDC2018SP-Trilha-UX-Feature-flags-e-Releases-controlados-4-320.jpg)
Uploaded bytdc-globalcode
TDC2018SP | Trilha UX - Feature flags e Releases controlados
Feature flags and controlled releases allow software features to be toggled on and off without deploying new code. The document discusses feature flags, their common uses, types including for release, operations, experiments and permissions. It provides examples from Moip and notes challenges like increased complexity. Feature flags can help reduce risks in continuous delivery by allowing gradual rollout of features.
TDC2018SP | Trilha UX - Feature flags e Releases controlados
- 1. pen4education FEATURE FLAGS AND CONTROLLEDRELEASES Eduardo Colabardini Chapter Leader @ Moip eduardocolabardini@gmail.com @ecolabardini Lucas Queiroz Software Engineer @ Moip lucascqueiroz97@gmail.com @lucascqueiroz97
- 2. pen4education Agenda • What arefeature-flags? • Common practices • Types • Longevity versus dynamism • Release flags • Real cases from Moip • Not a silver bullet • The superhero: IFMAN DEMO!
- 3. pen4education What are feature-flags? •Flags = Toggles = Bits = Flippers = Switches • Variables used in conditional statements / strategy pattern • A way to modify system behavior • Enable/disable features
- 4. pen4education Common practices • Compiled/ hardcoded users = ['user1', 'user2'] • Command-line arguments $ java MyApp user1,user2 • Property files users = user1,user2 • Relational databases > update user set role='admin' where id=1; • Key-value stores > sadd users user1
- 5.
- 6. pen4education • Release • Decoupledeployment from releasing • Canary releases - can be unstable, bleeding edge • Alternative to feature branches • Ops • Operational aspects of a system • Circuit-breaker • Experiment • A/B testing • Permission • Users permission, freemium model Types
- 7.
- 8. pen4education Release flags • Trunk-baseddevelopment • Continuous integration, delivery and deployment • Small commits / testing culture • Reduce deployment risks • Reduce costs of long lived branches • Escape from merge hell
- 9. pen4education Real cases fromMoip • Contestation central • Third party transfers • Two factor authentication • Checkout • OAuth 2.0 • Registered "boleto"
- 10. pen4education Not a silverbullet • Feature flag hell • More test scenarios • Keep track of feature-flags' states • Harder to support, debug and replicate problems • Technical debt - "Toggle removal task" onto the team's backlog • Expiration dates (TTL) / fail a test • Limit on the number of dynamic feature flags in a system
- 11. pen4education "Your first choiceshould be to break the feature down so you can safely introduce parts of the feature into the product. The advantages of doing this are the same ones as any strategy based on small, frequent releases." - Martin Fowler
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18. pen4education https://github.com/moip Eduardo Colabardini Chapter Leader@ Moip eduardocolabardini@gmail.com @ecolabardini Lucas Queiroz Software Engineer @ Moip lucascqueiroz97@gmail.com @lucascqueiroz97 Eduardo Colabardini Chapter Leader @ Moip eduardocolabardini@gmail.com @ecolabardini Lucas Queiroz Software Engineer @ Moip lucascqueiroz97@gmail.com @lucascqueiroz97 Dúvidas?