Senior Engineer and Game Architect,
2021/4~2022/7
Responsible for developing Game server and CMS system, the only backend engineer and architect in the team,
mainly responsible for backend development and design
, as well as backend/frontend development for the CMS system (Vue3).
⚫ Developed a total of 6 games, poker and electronic games during the employment period. In addition to main development work,
also developed and maintained a shared library for the entire backend,
occasionally performed cross-team code reviews, and provided suggestions to improve the performance of other team products.
⚫ The company's original backend logs were written into the Product's database, and the Game server logs were written into files and periodically uploaded to AWS S3.
Based on my experience, I actively discussed and recommended using AWS Athena with the operations team
, which resulted in the following improvements:
- The company's database-related costs decreased by 95%.
- No need to consume resources from other departments when searching for logs.
- Due to the structured nature of the logs, issues can be tracked faster and more accurately.
⚫ While actively helping with code reviews for other teams, I discovered a lack of locking concept in the company's wallet design, which resulted in over-deductions during high concurrency.
I proposed optimistic and pessimistic locking solutions to address this issue.
⚫ Initially, we used Redis to do lightweight message proxy services for our project, but I proactively introduced RabbitMQ to replace Redis, as RabbitMQ can ensure message delivery.