Skip to content
Harmonize IT

Case study · Financial SaaS

Case study: Multi-tenant financial SaaS with CQRS and DDD

For a European financial software vendor, we helped design and build a multi-tenant SaaS platform using CQRS and Domain-Driven Design on AWS. One platform now serves many client organisations with isolated data, per-client configuration and fast reporting.

Last updated:

Context

A European software vendor provides financial management software to public and private organisations. Its clients use it to manage debt, financing and financial risk, and rely on it for decisions and regulatory reporting.

The vendor was building a new generation of its product as a SaaS platform: one application, operated in the cloud, serving all clients.

Challenge

  • Strict tenant isolation. Clients entrust the platform with sensitive financial data. One client must never see, or influence, another client’s data.
  • A rich business domain. Financial instruments, schedules, rates and valuations follow precise rules with many variants. Errors are measured in money.
  • Two very different workloads. Users record and modify operations with heavy validation, and they also run large, flexible reports and simulations across the whole portfolio.
  • One codebase, many clients. Each client expects its own settings, permissions and reference data without a custom version of the product.

Solution

We worked with the vendor’s architects and product teams as senior engineers and technical leads.

Domain-Driven Design to tame the complexity. Together with business experts, we split the domain into bounded contexts, each with its own model and vocabulary. Developers and financial experts use the same words for the same concepts, and those words appear in the code.

CQRS where it pays off. Write operations go through a command model that enforces business invariants. Read operations use projections built for the screens and reports that need them. Reporting no longer competes with transactional processing, and each side can evolve and scale on its own.

Multi-tenancy in the foundations. The tenant is resolved at the edge of the system and carried through every layer: API, services, messaging and persistence. Data access is filtered by tenant at the infrastructure level, so a developer cannot forget it in a query. Configuration, permissions and reference data are tenant-scoped.

Cloud-native on AWS. Services are containerised and deployed on AWS with managed databases and infrastructure as code. Environments can be recreated on demand, which shortens testing and onboarding of new clients.

Leadership inside the team. Beyond writing code, we documented architecture decisions, set up coding standards and reviewed pull requests, so that the patterns were applied consistently by every team.

Outcome

  • One platform and one codebase serve all client organisations; no client-specific branches.
  • Tenant isolation is enforced by the architecture itself.
  • Heavy reporting runs on dedicated read models without slowing down day-to-day operations.
  • The domain model gives business experts and developers a shared language, which reduces misunderstandings in specifications.

This is the kind of work we do in Architecture & Modernization, often combined with Technical Leadership & Advisory to make sure the architecture is applied consistently.

Expertise behind this project

More case studies

EU public institutions

SAP integration for an EU institution

How we connected a Java and Angular business application to SAP and an e-signature service for a European public institution.

  • Java
  • Spring Boot
  • Angular
  • SAP

KYC and compliance

KYC platform for a global investment bank

Building the Java Spring Boot microservices and Angular front end of a know-your-customer platform for a global corporate and investment bank.

  • Java
  • Spring Boot
  • Angular
  • REST microservices

Have a similar challenge?

Tell us about your project, your contract need or the team you want to extend. We reply within two working days.