Anonymized case
Architecture of a digital platform with content, gamification, and a members area
The solution needed to combine content, users, rankings, and files in an app-like experience without overloading the server during uploads.
Scenario
A platform with a content library, users at different access levels, gamification (points, events, ranking), search, filters, and consumption in a PWA and on the phone. Large files could not live on the application disk as if they were email attachments.
Problem
Media volume and business rules in the same place. Ranking and scoring competing with file delivery. Notifications, permissions, and uploads without a clear design of where each responsibility lives. Content growth making search and listing the center of cost, not the layout.
Diagnosis
A platform of this kind breaks when the application server becomes storage, when ranking is recalculated at listing time with no cut, and when the members area treats permission as a screen detail. Gamification without history and without an anti-abuse rule becomes a useless ranking.
Solution
The technical decision was to separate what is a file, what is business data, and what is the app experience.
- Object storage for video and documents, with the application orchestrating access — not hosting the binary.
- APIs for content, users, scoring, and search, with cache where reads were repeated.
- Gamification rules as a persisted event, not as a loose calculation on the page.
- PWA for recurring use, with the same backend as the web operation.
- Access levels and a members area as real permission, not as CSS hiding a button.
Result
The platform started growing content without turning the application server into a media disk, and members, ranking, and search operations stayed in the API domain. We do not publish audience or revenue metrics. The public result is architectural: media, rules, and the app stopped being a single fragile process.
Technologies used
- Web application and PWA
- APIs
- S3-compatible object storage
- Relational database
- Search, filters, and notifications
Related services
Development, APIs, and infrastructure in the same cycle.