Tag • 18 Posts

Continuous delivery

Thumbnail for The 5 Phases of a Feature Launch
Industry Trends

The 5 Phases of a Feature Launch

Feature launches in leading engineering teams increasingly look like a ramp rather than a one time switch, going through dogfooding, debugging, max power ramp, scalability and learning phases.

Adil Aijaz
Thumbnail for Release Frequency: A Need for Speed
Industry Trends

Release Frequency: A Need for Speed

If your release train is moving slower than you would like, take a look at these three essential ingredients you should have.

Adil Aijaz
Thumbnail for Pros and Cons of Canary Release and Feature Flags in Continuous Delivery
Code

Pros and Cons of Canary Release and Feature Flags in Continuous Delivery

Canary releases (also “canary deployments”) and feature flag rollouts are two common feature release strategies for testing in the production environment, increasing the safety of continuous delivery, deploying faster and more often. Both aim to reduce the “blast radius” of unforeseen problems and build confidence in a new release. Both…

Dave Karow
Thumbnail for Engineering Burnout: What it is and how Experimentation and Continuous Delivery can help
Industry Trends

Engineering Burnout: What it is and how Experimentation and Continuous Delivery can help

The effects of burnout can be significant for any software development organization, large or small. In this blog post, we discuss how burnout can be alleviated with an agile workflow powered by feature flags, a robust feature experimentation platform and incremental feature rollouts using continuous delivery.

Henry Jewkes
Thumbnail for Shift Right with Feature Flags: Best Practices for Testing in Production
Industry Trends

Shift Right with Feature Flags: Best Practices for Testing in Production

The shift-left testing emphasizes test execution early and often, providing rapid feedback to development teams for each new code commit. Shift-right extends application testing into the production environment. Learn about the benefits and recommended best practices of using feature flags to support Testing in Production.

Lenore Adam
Thumbnail for Managing a Monolith Breakup – Stateful Services
Infra

Managing a Monolith Breakup – Stateful Services

This is one post in a series about managing the breakup of a monolithic architecture into a small service. In the first post of the series we looked at some fundamental techniques which allowed us to perform this sort of broad architectural shift as a series of small, safe steps. We started off…

Pete Hodgson
Thumbnail for Managing a Monolith Breakup
Infra

Managing a Monolith Breakup

This blog posts describes the sequence of changes a team can use to extract a chunk of functionality out from a monolith while continuing to deliver features and functionality in parallel.

Pete Hodgson
Thumbnail for Enhancements to Team Workflows in Split
Features

Enhancements to Team Workflows in Split

With Split’s improved invite flow it is now easier to invite your entire team and assign teammates to groups at the time of invitation. You can now invite multiple teammates at once and assign them individually or in bulk to groups, simplifying your team’s onboarding to Split.

Trevor Stuart
Thumbnail for Where to Put your Feature Flag?
Code

Where to Put your Feature Flag?

Feature flags are a necessary part of your Continuous Delivery (“CD”) pipeline. In fact, as your team grows, you can’t do CD without feature flags. This article provides best practices on when to use feature flags.

Adil Aijaz

Stay up to date

Don’t miss out! Subscribe to our digest to get the latest about feature flags, continuous delivery, experimentation, and more.

Ready to get started?

Start using Split for free today. No credit card required.