Lead Developer 01/2021 - 09/2023

CommunityEngine

An asynchronous backend and frontend structure for a large community. Lua, JS & SQL Optimization.

Explore Case

Taking responsibility for
Live Systems during my studies

A massive project over two and a half years (01/2021 – 09/2023) where I learned what it takes to build an architecture that must perform under the pressure of real users creating big data continuously.

The focus lay on developing server-client logic in Lua and perfectly structuring data maintenance during live operation. A bug must never crash economies or inventories.

Lua/JS Core Logic
SQL Database
2.5 Yrs. Ops.
server_core.lua
1-- Handling event-driven SQL queries for High-Traffic 2RegisterNetEvent('core:updatePlayerState', function(source, payload) 3 local _src = source 4 local queryId = OptimizeQuery(payload) 5 6 -- Ensuring Data Integrity via transactions 7 MySQL.Async.execute('UPDATE users SET state=@state WHERE id=@id', { 8 ['@state'] = payload.current_state, 9 ['@id'] = payload.user_identifier 10 }, function(rowsChanged) 11 if rowsChanged > 0 then 12 LogData("Success", _src) 13 end 14 end) 15end)

High-Traffic
Architecture

Preparing internal knowledge bases and keeping event listeners clean.

SQL Query Load

Thousands of queries hitting the database required serious SQL Optimization strategies.

🛡️
Strategy Asynchronous caching layers and carefully designed indexes prevented bottlenecks in live operation.
📦

Versioning

Strict release management and versioning through Git ensured smooth updates.

🛡️
Workflow Separation of development, staging and live branches. Documentation of updates for the moderation team.
🤝

System Support

Technical support and systematic troubleshooting (2nd-Level) of bugs reported by the active community.

🛡️
Operations An active ticket system and logging helped identify and reproduce use-case bugs.