Database Reference
In-Depth Information
Design an Hbase table/schema for the following real-world example.
We all know that the classical approach in the SQL world would be to put all the
students in one table and all the courses in another and to have a join table, named
appropriately as
STUDENT_COURSE
, which will indicate their relationship. However,
as discussed in
Chapter 6
,
Denormalization Use Cases
, it is preferable to avoid joins in
big data, since they are very expensive computationally.
The timer signiies that you need to close the topic now and think about the
approaches that you can take, perhaps sketch them. Team competition works great,
and if you are a teacher, you can assign this problem to teams of students.
