Client: LedgerWorks · DevOps, SRE & Cloud · UK payments fintech (150 staff)

Shortening the Release Cycle of a Payments Monolith

By TechSupport Team. Published November 16, 2026. Updated .

TechSupport Team supported LedgerWorks as it split parts of its Java payments monolith into separately deployable services. Over seven months, the client’s ArgoCD records show the release cycle falling from six weeks to three days. GitHub Actions recorded fewer deployment failures.

Client and engagement facts

Client
LedgerWorks
Industry
DevOps, SRE & Cloud
Business context
UK payments fintech (150 staff)
Delivery model
DevOps support
Application
Payments monolith migrating to microservices
Supplied geography
UK
Company size in source
150 staff

Application stack and tools

Application stack

  • Java/Spring
  • Kubernetes
  • PostgreSQL
  • AWS

Tools used

  • Argo CD
  • GitHub Actions
  • Datadog
  • Terraform

Why Support Was Needed

The original release depended on one pipeline and a shared database. The team extracted services from the edges and gave each service an isolated schema and its own pipeline.

Technical Work

  • Extracted services at the edges of the monolith first.
  • Split the shared database into isolated schemas.
  • Built a separate CI/CD pipeline for each extracted service.

Representative Incident

Splitting the shared database added six weeks to the plan. The team reviewed the new scope with the client, which accepted the revised schedule.

Results and how they were measured

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSource and scope
Release cycle6 weeks3 daysBaseline: weeks; Result: days7 monthsClient ArgoCD
Deployment failures21%4%%7 monthsClient GitHub Actions; Scope: The seven-month comparison excludes one cloud-region deployment failure.

Evidence and Limitations

The seven-month comparison excludes one cloud-region deployment failure.

Schedule Impact of the Database Split

The team reviewed the timeline with LedgerWorks after the database split added six weeks to the plan.

Scope a Similar Engagement

Share your release cycle, shared dependencies and the changes that need separate deployment approval. Request a support plan or explore DevOps support.

Get a technical support plan

Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.

  • We reply by email.
  • We agree a call about the roles, your stack and the hours.
  • If there is a fit, we propose engineers after an assessment.

A short outline is enough. Add your stack and coverage hours if you know them. Do not include credentials or customer data.

Add coverage and team details

We use these details only to reply to you. Describe the application, stack and hours you need covered. Keep credentials and sensitive technical data out of this form. We save the brief for delivery and use Telegram to notify our team.