0 views collected around this technical thread.
Laravel Pennant, introduced with Laravel 10, provides a robust feature‑flag system that lets developers gradually roll out new functionality, perform A/B testing, and implement trunk‑based development strategies, with examples showing both closure‑based and class‑based definitions, controller usage, and middleware integration.
This article introduces Laravel Pennant, the official feature‑flag package for Laravel 10, explains its benefits for gradual releases and A/B testing, and provides clean code examples showing how to define and use feature flags within service providers, controllers, and middleware.
This comprehensive overview introduces Apache Superset 2.0, covering its history, core features such as SQLLab, extensive visualizations, data‑exploration capabilities, dashboard creation, native filters, custom plugins, feature flags, and practical demos, while also providing tips, Q&A, and community resources for developers and data engineers.
This article explains progressive delivery and feature‑flag based smart release, showing how controlled rollout pace and stage authorization reduce deployment risk, enable rapid iteration, and integrate with CI/CD, A/B testing, and monitoring for safer software releases.
The article explains how Google’s continuous delivery practices—such as modular architecture, feature flags, gray‑scale deployments, rapid feedback loops, and a culture of always‑ready‑to‑deploy—enable faster, safer software releases while reducing risk and cost.
The article explains how Google treats development speed as a team sport, using modular architecture, continuous integration, feature flags, gray deployments, production‑like testing, and data‑driven decisions to enable frequent, small releases that improve quality, reduce risk, and lower costs.
The article explains how Facebook uses the GateKeeper configuration system to perform safe, incremental rolling releases of new features, describing the release stages, constraint‑based switch logic, integration with external data stores, and the trade‑offs between flexibility and operational risk.
Feature flags enable controlled system changes, allowing teams to monitor business and technical metrics, quickly roll back harmful updates, and operate within a rapid feedback loop that informs subsequent iterations, though many modern product teams struggle to integrate flag platforms with analytics systems for richer insights.
Feature flags enable controlled system changes, allowing teams to observe business and technical impacts, retain beneficial updates, quickly roll back harmful ones, and continuously learn through a fast feedback loop that guides subsequent modifications.
This article outlines practical guidelines for creating clear feature‑flag names, establishing management processes, implementing retirement plans, detecting stale "zombie" flags, assigning ownership, and using metadata tags to keep feature‑flag systems maintainable and low‑risk.
The article explains how to use feature flags in a three‑tier microservice architecture, describing the need for both high‑level end‑to‑end tests and low‑level unit tests within CI/CD pipelines to ensure correct behavior when flags are on or off, while avoiding excessive test combinatorial explosion.
The article explains how an e‑commerce company can use a single feature‑flag named “free‑delivery‑banner” to selectively show or hide a free‑delivery banner on the homepage, coordinating across product, delivery‑cost, and marketing teams while minimizing cross‑team dependencies.
This article examines how to locate the free‑shipping feature‑flag decision in an e‑commerce system, arguing that the decision should be made at the web‑layer where user context is available and then passed to the checkout service, keeping each service focused on its core responsibilities.
Choosing whether to evaluate feature flags on the server or the client impacts performance, configuration latency, security, and implementation complexity, with server‑side decisions generally offering better speed, reduced cache‑invalidation risks, protected data handling, and simpler architecture, especially for web and mobile applications.
When a user moves from an anonymous to a logged-in state, maintaining consistent feature‑flag behavior—such as discount eligibility—requires strategies like assigning a persistent visitor ID via cookies to link the two sessions and ensure a seamless experience.
This guide explains how to keep a feature flag's assignment consistent for individual users as exposure percentages increase or decrease, using a new "Previously Seen Products" section on an e‑commerce search page as a practical example.
The article explains how Azure DevOps teams separate application deployment from feature rollout using feature flags, enabling granular control, early user feedback, rapid rollback, and a staged release process without redeploying the application.
The article chronicles Microsoft’s Global Development Platform Engineering team’s transformation from an Agile‑focused process to a DevOps‑driven culture, detailing the 2013 Visual Studio 2013 launch, the ensuing service outage, multi‑region scaling, canary deployments, feature‑flag controls, Git‑based branching, Scrum adaptations, and data‑driven experiments that dramatically improved service reliability and user onboarding rates.
The article recounts Visual Studio Online’s 2013 launch outage, explains how Microsoft adopted multi‑region scaling, canary releases, continuous integration, and feature‑flag patterns to transition from Agile to DevOps, and shows how these practices dramatically improved service stability and accelerated product delivery.
The article describes Dropbox’s Stormcrow system, a configurable feature‑gate platform that enables fast, safe rollout of new functionality across web, desktop, and mobile clients, supports granular A/B testing, leverages custom data fields, and integrates deployment, monitoring, and audit tooling for large‑scale operations.