Vlad Kampov gave a presentation on using feature toggles, AB tests, and static overrides instead of separate test, staging, and production environments. He argued that maintaining separate environments is costly and can lead to inconsistencies. Instead, his proposed approach uses feature flags and configuration overrides to control features in a single environment. The presentation concluded with a demo and Q&A discussion of the tradeoffs between a single environment approach versus maintaining separate test, staging, and production environments.

2. Vlad Kampov @ React fwDays ‘23
Feature Toggles, AB-Tests, Static Overrides
Do you really need
your test env?

3. (on the right)
Vlad Kampov
• Love music and running
• Respect memes
• Host of the “Подкаст ЖеПеТе”
• Senior UI Engineer @ Netflix
• Екс Frontend Guild Engineering
Manager @ Wix.com

4. ⚠ Opinions are my own and don’t
represent the official position of my
employers (current and previous)

5. “Oh, but it works on
my machine”

6. “Oh, but it works on
staging”

7. Environments

8. • Local
• Testing
• Staging
• Production
Common Pattern

9. Dev Environment

10. Testing Environment

11. Staging Environment

12. Production Environment

13. Common flow

14. THE PROBLEM

15. • High cost
• Inconsistency of the data
• False-positive tests
• Everything that isn’t a production
Main factors

16. Feature Toggles

19. AB-Tests

21. Static Overrides

22. /?overrides={"toggles":{"newCardDesign":true}}

23. Microfrontends

24. microfrontend1 microfrontend2
header (also microfrontend)
root config

25. How it’s all connected

26. Cons for The One Env

27. • Rollbacks
• What’s with the backend?
• Security?
• … just bring them at the Q&A
Cons for The One Env

28. Pros for The One Env

29. • Rollbacks
• What’s with the backend?
• Security?
• … just bring them at the Q&A
Cons for The One Env

30. DEMO TIME

31. That’s it?

32. bento.me/kampov