Back-End Engineer (Database): choose between SQL vs NoSQL

Nimbus Commerce is a fast-growing e-commerce startup focused on transforming online shopping through advanced technology. With over 250,000 active users and 50,000 monthly transactions, the company is preparing for rapid expansion and the launch of a new mobile app. This app will feature personalized recommendations, real-time inventory updates, and integration with social media reviews. The technical stack is built on Python, JavaScript, Django, and React, with AWS services supporting operations. However, recent high-traffic events exposed limitations in the current SQL-based database, especially in handling unstructured data like user reviews and images. The new app must efficiently manage both structured and unstructured data, scale to meet surges in demand, and be easy for the small, agile team to adopt.

You take on the role of a junior developer at Nimbus Commerce, joining a one-on-one technical discussion with the Tech Lead. Your task is to analyze the requirements for the new mobile app and recommend the most suitable database architecture—SQL, NoSQL, or a hybrid approach. You'll need to weigh the pros and cons of each option, considering scalability, consistency, data structure, and the team's expertise. During the conversation, you must clearly present your recommendation, justify your reasoning, and respond to follow-up questions or challenges from the Tech Lead, demonstrating your understanding and adaptability.

• Engage in a real-time chat with the Tech Lead to discuss database architecture options.
• Clearly explain the advantages and drawbacks of SQL and NoSQL databases for the company’s needs.
• Justify your recommendation based on technical and practical considerations.
• Respond effectively to questions and challenges, showing critical thinking and professional communication.