I design and build high-performance software with a focus on server-authoritative multiplayer systems, distributed architecture, concurrency, networking, and data-oriented simulation.

I'm currently developing Zolian - Age of Ruin, a server-authoritative MMORPG built around Unity's ECS/DOTS architecture. Much of my work centers on scalable world simulation, server infrastructure, persistence, networking, and extracting as much deterministic performance as possible from C# systems.

• MMORPG architecture : authoritative servers, world layering, sharding, simulation, and distributed services
• Data-oriented design : Unity ECS/DOTS and highly parallel simulation workloads
• Backend systems : modern C#/.NET, asynchronous I/O, concurrency, and service architecture
• Networking : multiplayer replication, server authority, state synchronization, and network performance
• Persistence : SQL Server architecture, stored procedures, data access, and high-throughput persistence
• Performance engineering : profiling, allocation reduction, cache-aware design, and workload scaling

Zolian - Age of Ruin is my current long-term engineering (passion) project: a modern MMORPG designed around a server-authoritative, data-oriented architecture.

The project is an ongoing exploration of the engineering problems that make persistent multiplayer worlds interesting to build:

• Large-scale authoritative simulation
• ECS/DOTS-based world processing
• World layering and horizontal scalability
• High-concurrency server workloads
• Multiplayer networking and replication
• SQL-backed persistence
• Server lifecycle and infrastructure
• Observability and production performance
• Deterministic, allocation-conscious systems design

The current game and infrastructure are being developed privately while the architecture continues to evolve.

• M.S. Software Engineering
• B.S. Security Risk Analysis, Minor in Cybersecurity

My background in software engineering and cybersecurity heavily influences how I approach backend architecture: clearly defined trust boundaries, server authority, defensive validation, deterministic behavior, and systems designed for failure rather than assuming it cannot happen.