Skip to content
NJNakshatra Joshi
← All work
Production/2025

GoBrics Hackathon Platform

Multi-region platform for 10K+ users across India and Russia

Route 53→region→upload API→S3 / Yandex→Redis queue→email
10K+
users
1K+
concurrent
2
cloud regions

The problem

One hackathon, two countries, and a data-residency requirement: Russian participants' data had to stay on Russian infrastructure, while the product had to feel like a single platform to everyone.

Approach

01

One storage codebase, two clouds

Yandex Object Storage is S3-compatible, so the same S3-SDK code path serves both regions with different endpoints and credentials rather than a forked storage layer.

02

Routing as the residency boundary

Co-designed Route 53 geolocation routing so a request lands in the right region before it touches application code — residency becomes a DNS and configuration property instead of a conditional scattered through handlers.

03

Queue the email, respect the quota

Submission confirmations go through a Redis queue shaped to Resend's rate limits, so a burst of 1K+ concurrent submissions does not translate into a burst of dropped emails.

Outcome

  • 10K+ users across India and Russia, peaking above 1K concurrent.
  • PDF submissions and confirmation emails held through peak load.
  • Russian participant data stayed on Yandex Cloud without forking the application.

What I'd do differently

Geolocation routing is invisible when it works and very hard to debug when it doesn't. Next time I would ship a region-echo endpoint on day one.