Right in the middle was AWS re:Invent, November 27-30. The Split booth at re:Invent attracted a ton of traffic. We gave away about 1000 t-shirts! As our t-shirts say, our message at the event was simple, but powerful, “Test Everything. Results Matter.”
But before diving into our own message at re:Invent, it was exciting for us to see Amazon.com CTO Werner Vogels talking about our foundational technology. Split, at its foundation, uses a technology called “feature flags” or “feature toggles,” to control the visibility of features to users. Werner brought up feature toggles as one of best practices for automating deployments.
As Werner explains, “Feature toggles is the mechanism where you deploy the new code or the new system, but you don’t enable the new code. And you slowly start toggling on features one by one to see how they impact your customers.”
From Feature Flags to Feature Experimentation
Right after Werner talked about automation and resilience, he introduced Nora Jones, Co-author of the book “Chaos Engineering” and Senior Software Engineer at Netflix to the stage. Nora spoke about the famed processes that Netflix has in place to deliberately introduce failures into their systems to test resilience and failover.
Chaos testing for infrastructure resilience has become more commonplace for many leading online services and cloud applications. And, automated code testing as part of deployment is also commonplace. You might think that between testing infrastructure and testing code you have all your bases covered. However, there is a major missing link in this picture. What about customer experience? What about the impact of a code release to the business? Your code might deploy fine, but if the intended feature misses the mark or causes a poor customer experience, isn’t that just as much of a failure?
If you connect the dots between feature flags and a culture of testing and experimenting on everything, the net result is continuous feature experimentation. As we announced a few weeks ago, the Split Feature Experimentation Platform is bringing together these two worlds.
Bringing our Message to AWS re:Invent
We demoed our new feature experimentation platform at the event, and the response was overwhelming. Engineering leaders saw the value of controlling the blast radius of a new feature, by only exposing it to beta customers or even doing a percentage-based roll-out to users that match specific attributes. With that small of an exposure to the user base, the impact would not be easily measurable in APM tools. However Split ingests all the event data you care about, letting you see the impact key metrics like page load times for just the precise population that was exposed to a new feature.
No need to configure experiments across 2-3 different tools anymore. Split shows you all the metrics you care about in one place, automatically configured for an experiment.
At the same time, product leaders saw the value in seeing the impact of a new feature on things like product usage metrics, or even helpdesk or support tickets. This gives a product manager a complete view of the impact of a new feature, on both the direct metrics the feature was intended to impact along with broader metrics that matter to the organization as a whole.
Continuing the Conversation
We told a compelling story at re:Invent. Whether you stopped by our booth or not, we’re excited to keep the conversation going. Follow us on LinkedIn or Twitter to continue to get updates on what’s new in the platform. Or, watch the video of Split CEO, Adil Aijaz giving a talk at Split customer Vevo HQ on “Building a Culture of Experimentation.”
If you didn’t catch it live, here’s a quick video of the demo.
Stay up to date
Don’t miss out! Subscribe to our digest to get the latest about feature flags, continuous delivery, experimentation, and more.
Become more data-driven around feature releases by using impression data from Split in mParticle and mParticle event data to evaluate treatments in Split.
Learn how Walmart uses product experimentation as a way to increase engineering impact and progressive delivery as a way to reduce the risk of moving fast.
Over the past few months we’ve been out in the field, chatting with development and operations teams from more than 100 different organizations around the U.S. We wanted to know how they get software to market. How often do they release new features to their users? How often do they…