Feature toggles in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a feature toggle in software development?

A feature toggle is a technique that allows turning features on or off in a software system without deploying new code. It helps control feature availability dynamically.

beginner

Name two common types of feature toggles.

Two common types are:<br>1. Release toggles - control feature rollout.<br>2. Operational toggles - control system behavior like enabling/disabling caching.

intermediate

Why are feature toggles useful in microservices architecture?

They allow independent deployment and gradual rollout of features across services without downtime, enabling safer releases and easier rollback.

intermediate

What is a potential risk of using feature toggles if not managed properly?

If toggles are left in code too long, they increase complexity and technical debt, making the system harder to maintain and test.

advanced

How can feature toggles be implemented in a distributed microservices system?

They can be implemented using a centralized configuration service or feature flag management tools that services query at runtime to decide feature state.

What is the main purpose of a feature toggle?

A To improve database performance

B To monitor network traffic

C To encrypt user data

D To enable or disable features without redeploying code

Feature toggles allow turning features on or off dynamically without new deployments.

Which type of feature toggle controls system behavior like caching?

A Release toggle

B Operational toggle

C Experiment toggle

D Permission toggle

Operational toggles control system behaviors such as caching or logging.

What is a risk of keeping feature toggles in code too long?

A Improved system security

B Reduced code complexity

C Increased technical debt

D Faster feature rollout

Old toggles increase complexity and technical debt, making maintenance harder.

In microservices, how are feature toggles typically managed?

A Using a centralized configuration or feature flag service

B Hardcoded in each service

C Through database triggers

D By manual code changes only

Centralized services allow consistent toggle state across distributed microservices.

Which of these is NOT a benefit of feature toggles?

A Automatic bug fixing

B Instant rollback without redeployment

C Testing features in production

D Safe gradual rollout of features

Feature toggles do not fix bugs automatically; they control feature availability.

Explain what feature toggles are and why they are important in microservices.

Think about how toggles help release features safely without downtime.

Describe how to implement feature toggles in a distributed microservices environment and mention potential risks.

Consider both technical setup and maintenance challenges.