SQL vs NoSQL Case Study
Group Members:
Rupani, Paras
Manchala, Vikas
Mallampati, Phani Krishna
Danda, Lohith Reddy
Cherukupalli, Krishna Vamsi
A) Main Data Sources in the Game
Bookings: Guest reservations, check-in/check-out dates, payment
information, and room assignments.
Customer Preferences: Dietary needs, room preferences, special
requests.
Staff Shifts: Employee schedules, roles, and work hours.
Supplies: Inventory levels, order history, and supplier details.
Customer Reviews: Text reviews, ratings, timestamps, and guest
identifiers.
B) Type of Data (SQL or NoSQL):
Data Bookings Customer Staff Supplies Customer
Source Preferenc Shifts Reviews
es
Type SQL NoSQL SQL SQL SQL
C) Data Source Reasoning
Bookings (SQL): Ideal for structured, relational data like guest-room
mappings and payments.
Customer Preferences (NoSQL): Handles varied, semi-structured
data like dietary restrictions.
Staff Shifts (SQL): Best for predictable, relational schedules.
Supplies (SQL): SQL suits structured data
Customer Reviews (SQL): Structured data with consistent fields
(e.g., ratings, timestamps, guest associations).
D) Advantages and Disadvantages:
Data Databa Advantag Disadvanta
Source se Type es ges
Bookings SQL Strong Rigid
consistenc schema
y and limits
integrity. adaptability.
Customer NoSQL Flexible Weaker
Preferenc schema for consistency
es evolving for
data. transactional
data.
Staff SQL Accurate Difficult to
Shifts relational adapt to
data schema
handling. changes.
Supplies SQL Efficient Poor
for handling of
structured unstructured
inventory data.
tracking.
Customer SQL Reliable Limited
Reviews structure support for
for unstructured
consistent text search.
analytics.
Data Descripti SQL Reasoning Pros and
Sources on or Cons
NoSQ
L?
Bookings Guest SQL Structured Pros:
reservatio and Strong
ns, check- relational consistenc
in/out, data (e.g., y, integrity.
payments. room
mapping). Cons:
Rigid
schema
limits
adaptabilit
y.
Customer Dietary NoSQL Semi- Pros:
Preferenc needs, structured Flexible
es room data that schema for
preference varies evolving
s, special widely. data.
requests.
Cons:
Weaker
consistenc
y for
transaction
al data.
Staff Employee SQL Structured Pros:
Shifts schedules, and Accurate
roles, work repetitive relational
hours. with clear data
relationship handling.
s. Cons:
Difficult to
adapt to
schema
changes.
Supplies Inventory SQL Structured Pros
levels, inventory (SQL):
order (SQL) Efficient
history, for
supplier structured
details. inventory
tracking.
Cons
(SQL):
Poor
handling of
unstructur
ed data.
Customer Text SQL Structured Pros:
Reviews reviews, data with Reliable
ratings, consistent structure
timestamp fields. for
s, guest consistent
identifiers. analytics.
Cons:
Limited
support for
unstructur
ed text
search.
