Skip to content
Selected work

Case study 01 / 02

01 · SaaS Platform

RIZZ MARKETPLACE

A digital product and top-up marketplace built as a scalable SaaS platform.

RIZZ Marketplace is a SaaS platform for digital top-ups and virtual products. It brings catalog, ordering, and account management into a single product that merchants and customers interact with through a web storefront.

01

Overview

A marketplace where digital products are listed, ordered, and managed in one place. The platform is structured as a SaaS product so a shared codebase can serve multiple merchant accounts.

  1. 01Shared catalog for digital products and top-ups
  2. 02Order flow with status tracking and fulfillment
  3. 03Account and merchant management
02

Problem

Digital product marketplaces sit at the intersection of a storefront and a ledger. The hard parts are keeping stock and order state consistent under concurrent access, and keeping read-heavy pages responsive while billing, reconciliation, and notifications run outside the request path.

03

Solution

Built on Laravel 12 with a server-driven React interface delivered through Inertia. PostgreSQL holds the transactional core, Redis handles caching, sessions, and queues, and the entire stack runs in Docker for environment parity between local and production.

04

Architecture

  1. 01Laravel 12 application with separate service layers for orders, catalog, and accounts
  2. 02React frontend delivered via Inertia, with no separate SPA to manage or deploy
  3. 03PostgreSQL for transactional data and reporting queries
  4. 04Redis for cache, sessions, and queued background jobs
  5. 05Docker Compose for consistent local development and CI environments
05

Implementation

Core flows (browsing, ordering, and account management) are handled by Inertia pages so the product behaves like an application without the operational cost of a full SPA. Client-initiated actions use JSON endpoints, while slow or non-urgent work runs in queued workers to keep the storefront fast.

  1. 01Inertia server-driven pages for the main storefront flows
  2. 02Queue workers for fulfillment, notifications, and reconciliation
  3. 03Eloquent models with deliberate query strategies for catalog pages
06

Challenges

Keeping inventory and order state consistent under concurrent access, and preventing background work from leaking into the response path. A recurring theme was finding the right split between what belongs in the request and what belongs in the queue.

07

Outcome

A complete marketplace product covering catalog, ordering, account, and admin flows on a codebase designed to grow as a platform.