Here , You Make It Simple
Precautions :
- Case Study - You have to first study about the case you're going to solve . Like, Analyzing the system , Queries that can be asked , Issues might occur in a situation , what kinda data you're going handle in this system , etc
- Be Blank - Just be blank to design a NoSql database . Never have any idea about the structure of the database. Because , We're not going to bother about it anyways. That's why we go structure-less architecture .
- Read About NoSql : Why Nosql ? - Here You can understand in just few words ..
Here, We Go...
Step #1 : Ask Before the Task !!!
Yep, It's , You first Decide the queries before you go to the designing phase , Because here , We're going to design the database as per the Queries we're going to ask . So Be ready about the Queries you're going to ask from the user end .
Step #2 : Get Solution for the Queries !!!
But, Now ! We're going to design the database as per the queries we're going to ask . That sounds like awsome na ? That's the main hike for the nosql strategy . For Example
<?xml version="1.0"?>
<booklet>
<note>
<to>Tove</to>
<from>Jani</from>
<heading>Reminder</heading>
<body>Don't forget me this weekend!</body>
</note>
</booklet>
This is a simple example for a nosql data here you may refer for 130% of tomes more for <from> tag than any other tags .So You can put it on any other efficient place to retrieve it in an easy way
Step #3 : You Got The Answer !!!
Sounds pretty fast? . Yeah, Now easily you can get the values by setting the key values and getters and setters to the respected values . You can easily get it by the child node with parent node or easily get it by the Unique Key Value .
Thank You for looking out my blog ..
Comments are appreciated ..
contact : jeyvee02@gmail.com
