Use case – storing data

Now that we have learned how to use NoSQL, we must decide whether NoSQL databases are adequate for our book use case WWTravelClub application. We need to store the following families of data:

• Information about available destinations and packages: Relevant operations for this data are reads since packages and destinations do not change very often. However, they must be accessed as fast as possible from all over the world to ensure a pleasant user experience when users browse the available options. Therefore, a distributed relational database with geographically distributed replicas is possible, but not necessary since packages can be stored inside their destinations in a cheaper NoSQL database.
• Destination reviews: In this case, distributed write operations have a non-negligible impact. Moreover, most writes are additions since reviews are not usually updated. Additions benefit a lot from sharding and do not cause consistency issues like...