split.io/customercasestudy X SAFE LAUNCH / FEATURE FLAGGING / MICROSERVICE MIGRATION CUSTOMER CASE STUDY When WePay needs to make a change to its infrastructure or introduce a new feature, it has the potential to have a cascading effect that could impact user experience and the business's bottom line. Their release cadence was initially targeted for every week, then that slipped to every two, but they still found that schedule restricted major feature development. With Split, WePay can now ship new discrete features as often as they’d like, testing them first internally, then with select customer groups, before slowly ramping them to all of their customers. How WePay ? Ramped Up its ? Release Cadence ? & Migrated to Microservices ? Using Split. How WePay Ramped Up its Release Cad

Join for free to read