# Shortening the Release Cycle of a Payments Monolith

> 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.

- Publisher: TechSupport Team
- Canonical page: https://techsupport-team.com/case-studies/payments-monolith-release-cycle-devops/
- Updated: 2026-11-16

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

## 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

Related services: [DevOps support](https://techsupport-team.com/services/devops-support/)

## 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

Table: Reported results and their measurement scope

| Metric | Baseline | Result | Units | Measurement window | Source and scope |
| --- | --- | --- | --- | --- | --- |
| Release cycle | 6 weeks | 3 days | Baseline: weeks; Result: days | 7 months | Client ArgoCD |
| Deployment failures | 21% | 4% | % | 7 months | Client 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](https://techsupport-team.com/contact/) or explore [DevOps support](https://techsupport-team.com/services/devops-support/).

## Related pages

- [DevOps support](https://techsupport-team.com/services/devops-support/): The related service for this engagement.

## Contact

Request engineers from TechSupport Team or ask a question: https://techsupport-team.com/contact/
