Question about data modeling from results.json

@jrabello Great question.

To answer that question I will first address 2 things. Both of which you may be familiar with already

1) What does JSON stand for? 2) The difference between an array and an object.

1) --> JSON stands for JavaScript Object Notation. The key phrase is Object Notation. You should expect a response of an array of objects.

Ex. [{key:element},{key:element},{key:element}]

-- An array is an list, and an object consists of key pairs.

Array = [l1,l2,l3,l4];
Object = {
  key1 : element1,
  key2 : element2
};

An Object can contain an array, a number, a string, a boolean, or another object.

In order to find a value in an array you would have to know its place in the array (similar to a position in line). To find a value in an object you would need to know the value of the key (similar to yelling out the name of a person waiting in line).

Iterating through the entire array (similar to walking through a line to look for the person you are searching for) to find an element if you don't know its location is very tedious, isn't scalable. Why I feel it isn't scalable is if you had an array of 10000 elements. Iterating through the entire array to find the element would take a bit of time - in terms of computer processing (every second counts).

Compare this to an object where we know only the name of the key to access the element we want. We just call that key pair ex. obj.key1 to access element1.

When we send an http request to JSON we get a response that is organized the same way we organize objects in javascript.

Let me know if you have more questions.