The Challenge

Slow, rigid release cadence

WePay initially released features on a weekly cadence, later slipping to bi-weekly. Despite this schedule, major feature development was constrained by the need for rapid, smaller deliverables. Additionally, traditional release processes created risks of cascading issues across a vast network of merchants, applications, and users.

Monolithic architecture limitations

WePay’s monolithic infrastructure, built in PHP, hindered agility. Migrating to a modern microservices-based approach was necessary but fraught with risks of downtime and disruption, given the critical nature of payment services.

The Solution

Decoupling feature rollouts from code deployments

WePay adopted Split’s feature flagging capabilities to enable faster, safer releases. By deploying code in an “off” state, engineers could:

• Test new features internally before public exposure
• Gradually roll out updates to select customer segments
• Release features independently of marketing or press timelines

“Tying feature accessibility to releasing code makes a lot of bad things happen, like releasing code at midnight to match a press release. Split lets us decouple these processes and release features with the click of a button.”— Chris Conrad, VP of Engineering, WePay

Facilitating microservices migration

‍Split’s multi-language support was pivotal in WePay’s shift from a monolith to microservices. This approach allowed simultaneous operation of old and new systems, ensuring:

• Smooth transitions with no downtime
• Unified control across both PHP and new service languages
• Consistent user experiences during backend changes

Streamlined QA with control groups

‍When a code release caused an increase in declined credit cards, Split’s control groups quickly isolated the issue. Engineers resolved the problem faster by comparing impacted users to unaffected control segments.

Results

Accelerated deployment cadence

‍WePay transitioned from bi-weekly releases to deploying new features as often as needed. This enhanced their ability to:

• Deliver incremental updates without impacting overall system stability
• Take on ambitious projects without fear of slowing down

“We’ve completely eliminated the need for midnight hotfixes. Split’s tools ensure we can release features safely and recover quickly if issues arise.” - Chris Conrad, VP of Engineering, WePay

Improved user experience

‍Controlled rollouts ensured a seamless user experience, even during significant backend transitions.

Increased engineering focus

‍By outsourcing feature flagging to Split, WePay engineers concentrated on core projects, eliminating the overhead of maintaining custom solutions.

‍Looking Forward

‍WePay’s adoption of Split has laid the foundation for sustained innovation. Engineers plan to continue leveraging Split by Harness to foster a culture of experimentation, and to make data-driven decisions that directly enhance customer and business outcomes.