# Taptok — Scaling a Multi-Tenant SaaS to 100K+ Monthly Transactions on AWS

> Taptok's digital business card platform was approaching the limits of a single-database architecture. Analytical queries were competing with transactional queries, and both were getting slower. We built tenant-based database sharding, decoupled analytics entirely, and maintained TDD throughout — making the rebuilt system safe to keep improving.

## Project context

- Client: Taptok for Business
- Industry: SaaS / Digital Business Cards
- Year: 2024

## Challenge

Single-database architecture was approaching capacity. Long analytical queries competed with transactional queries for I/O and locks — active users experienced slowdowns during report generation. Without test coverage, modifying core transaction logic was risky. Scaling vertically was becoming expensive and had a ceiling.

## Solution

Tenant-based sharding with consistent hash routing — horizontally scalable, application-transparent. Analytics decoupled to Redis event pipeline → background aggregation → reporting store. Zero analytical query load on the transactional database. TDD enforced throughout rebuild — comprehensive test coverage on all core transaction paths.

## Services

- Web Development

## Published results

- 100K+ Monthly transactions handled (on AWS infrastructure)
- 0 Analytical query impact on tx DB (fully decoupled)
- sub-second Transactional response time (under any report load)
- comprehensive Test coverage (core paths) (TDD enforced)

## Benefits

- Horizontal sharding — scale by adding shards not servers
- Analytics fully off the transactional database
- AWS (EC2, RDS, Docker) production infrastructure
- TDD throughout — safe to change, safe to ship

## Source and contact

- Canonical project page: https://qualityx.co/en/portfolio/taptok-saas-platform
- Discuss a related project on WhatsApp: https://wa.me/905392376734