Backend Developer: learn how to adopt NoSQL in an existing project
AnthroposAtlas Ticketing’s community features are straining the MySQL backend, risking platform reliability and scalability.
Unstructured data from photos, reviews, and surveys is causing performance bottlenecks and operational concerns.
Your goal is to justify a data migration strategy and present a scalable NoSQL solution to key stakeholders.
You are a Backend Developer at Atlas Ticketing, a global event technology company.
Atlas Ticketing is a global leader in ticketing technology, supporting millions of users daily with a high-performance platform for event management and attendee engagement. The company’s MySQL backend is optimized for structured transactional data, ensuring reliability and speed for ticket purchases and seat reservations. Recently, Atlas Ticketing has expanded to include community features—event photos, reviews, and surveys—which have rapidly increased in usage and introduced new scalability challenges. These features generate large volumes of unstructured data, causing performance bottlenecks and risking the platform’s reputation for reliability. To address these issues, Atlas Ticketing is considering migrating community-related data to a NoSQL database, aiming to improve scalability and maintain operational excellence.
You play as a Backend Developer tasked with proposing a migration strategy for Atlas Ticketing’s community features from MySQL to NoSQL. Your mission unfolds in two key interactions: first, you’ll chat one-on-one with the Head of Infrastructure, who is skeptical about moving data off MySQL. You must justify which data sets should remain on MySQL and which should transition to NoSQL, addressing concerns about reliability, consistency, and operational risks. Next, you’ll join a voice call with the Senior Engineering Lead, who is supportive and interested in your high-level NoSQL strategy. You’ll discuss data modeling approaches, query optimization, and operational safeguards, demonstrating your readiness to guide the migration and refine your approach with expert feedback.
- Engage in a focused chat with the Head of Infrastructure to justify your data separation decisions and address concerns.
- Participate in a voice call with the Senior Engineering Lead to outline and discuss your NoSQL strategy for scalable community features.
- Demonstrate clear technical communication and a solid understanding of NoSQL concepts.
- Show readiness to lead the migration by presenting a balanced and well-reasoned strategy.