White Hat Gaming Ltd – Enterprise Backoffice Platform

White Hat Gaming case study — Building and maintaining the enterprise backoffice and shared UI library in an Nx monorepo

Client:

White Hat Gaming Ltd

Date:

2021–Present

Duration:

4+ years
White Hat Gaming Ltd – Enterprise Backoffice Platform
Ongoing full-stack work on the White Hat Gaming backoffice platform, the internal system the business runs on. Frontend architecture, system design, and the shared-code practices that keep several teams from diverging.

About the client

White Hat Gaming supplies regulated online casino and sportsbook platforms to operators worldwide. Regulated is the operative word: compliance is a functional requirement here, not a policy document.

Project Overview

The backoffice is the internal system where operational, regulatory and business workflows actually happen. Several teams and several products all reach into it, which makes it the place where architectural decisions have the widest blast radius.The frontend is component-based and handles data-dense interfaces. Node.js and Scala sit behind it, with PostgreSQL underneath. The data volumes are large enough that predictable behaviour matters more than clever behaviour.The part I find most interesting is the monorepo. It runs on NX, with multiple applications and shared libraries in one codebase. That is the right call at this size, and it comes with a specific cost: a change to a shared library is a change to everything importing it, so the discipline around shared code has to be real rather than aspirational.The platform never stops changing. New features, new regulatory requirements, new internal tooling, and none of it is allowed to destabilise what is already running.

The Challenge

Complexity at scale is the recurring problem. The backoffice covers a wide range of workflows and user roles, and without hard separation of concerns that variety turns into a codebase nobody can safely change.The monorepo adds coordination on top. Changes cross application boundaries and multiple backend services, so consistency and communication do as much work as the architecture does.

My Contribution

Full-stack engineer, weighted towards frontend architecture and system design. I design and evolve the frontend structures, build the more complex UI workflows, and try to keep decisions defensible over years rather than sprints.I build reusable components and patterns suited to enterprise backoffice work, which is its own genre with its own rules.I work closely with the backend teams on Node.js and Scala, and with the NX monorepo setup that holds it together. Code review and mentoring come with it, which at this scale is part of the architecture rather than a separate activity.

Technology Stack

  • Vue.js, Node.js, Scala, PostgreSQL, NX monorepo, full-stack enterprise architecture, large-scale backoffice systems
Tags
Categories

Read More

Tell me about your project and get a price, timeline and project scope by email — no call needed.
Like what you see? Let’s work together

    How it works
    1. Tell me about your project below.
    2. I'll email you a few quick questions (about 3 minutes).
    3. You get a price, timeline and project scope by email — no call.
    A link helps me scope your project faster.

    Complete the short questionnaire to receive your indicative price, timeline and scope by email.

    This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.