Database Architecture
Structured athletes, clubs, managers, events, registrations, and historical records using MySQL and Laravel migrations.
← Back to selected work
Case Study 02 · Web Application
Arena-OKU
Turning a WhatsApp-based karate event workflow into a centralized web application for athletes and event organizers.
Before → After
From scattered chat records to a reusable operational system.
Before
WhatsApp↓Manual registration↓Scattered records↓Manual recap
After
Online registration↓Centralized MySQL database↓Admin management↓Automation + historical records
Technical problem solving
What I actually solved.
The project started as an academic thesis, then expanded into a real client implementation as deeper operational requirements emerged.
Bulk Data Migration
Supported importing historical athlete and event data so admins did not need to rebuild records manually.
Queued Airtable Sync
Used Laravel Queue so bulk uploads did not wait for external Airtable synchronization to finish.
Production Deployment
Prepared cPanel deployment, SMTP, cron, database setup, production build, and troubleshooting documentation.
Email Automation
Implemented email OTP and H-1 event reminder flows using Laravel Mailer / SMTP.
Testing & Documentation
Created Laravel feature/API tests plus schema dump and ERD documentation.
Stack
Built to work in a real operational environment.
LaravelPHPBladeViteMySQLAirtable APILaravel QueueSMTPPHPUnitcPanel
The operational value is simple: organizers can keep athlete, club, manager, and event records in one system, bring historical data forward, and reduce repetitive manual administration for future events.