Nowadays data and arrays are part of my daily diet as a front-end developer. But I still remember all that early confusion. My aim here is to give a high-level overview designed for people who have no engineering background. And to place it all in a realistic context.
In this article, we will talk about what data is and how we organise it. We will examine data structures focusing only on arrays to keep things clear. And we will look at why we need it.
Let’s imagine that we are working on an online platform that allows us to do our supermarket shopping from a website. That's a real-world application of the things we want to talk about here.
Take a look at example website, for an example of how this would look like.
Our website is going to show a list of products. This is going to be our starting point to talk about data and organising it in a context that mimics things we do every day in the front end.
What even is data?
Before we start talking about how we organise data, let's try to understand what data means in our context. And where this data comes from.
When you are working in the digital domain it’s helpful to remember that everything is data. Everything is bits stored in binary.
Now while that might be interesting, it is so general that it is of no help to us. So for our purposes, we will focus on a narrow idea of what data is. The one which is most immediately relevant. Take a look at the following list:
List of products
This reduced list is an example of the kind of products you can find on this website we are building. This list is our data: mushrooms, steak, fish, aubergines, and lentils.
So where does this data come from?
Data can live directly in your app, in your front-end code. But more commonly it comes from some outside source. Usually, this data is stored in a database.
The front end makes a request to the database and receives this data as a response. Once it has arrived into our front-end app, it is time for us to do what we need with it. For example, show the product name on the website, style it, and add any functionalities needed (such as an “add to cart” button).
Take a look at any of the popular shopping websites and you'll see the same pattern. It will have a list of products presented in a certain style with various functionalities and other information about it.
How do we organise data?
So we have established that this list of products is our data. Now we have to package this data in some sort of a container. This will enable us to organise it, move it around, and later access it and do stuff to it.
One of the most common ways to organise data that you will work with frequently is called an array. Here’s what an array looks like:
['mushrooms', 'steak', 'fish', 'aubergines', 'lentils']
The syntax looks simple enough. You create an array with the square brackets
. And separate the individual elements with a comma
,. If your data is made up of strings put each element inside quotes or double quotes
''. String loosely means a bunch of characters representing text, like words and sentences.
And that’s it. You have just organised your data in a single package called an array. And we can do lots of things with this now. You can think of an array as merely a container that allows us to put data inside, organise it in a certain structure, and permits us to do things with it.
An array is one example of what we call data structures. These are the various ways we use to organise data. There are a lot of them, but the two most common ones in the front end are arrays and objects.
So now what do we do with this?
Why do we need arrays?
We need arrays and other data structures in the front end because almost everything we deal with is data. And that needs to be organised in a way that we can work with.
In our example, once we receive the products' array we can write the logic that takes each product and displays its name on our website. But how do we select each item from the array and do things to it?
In the next article, I explain just that. I take our example to the next step and talk about how loops come into play to start processing our data - so look out for it!
So, to recap. For our online supermarket, we have a bunch of products and that's our data. We saw how we organise this data into data structures like the array. This is usually stored in a database. We can then request this data. And once it “arrives” to our front-end app from the database we can start processing it and doing things with it. Hopefully, this has given you a better idea of why we need this in our front end.
Of course, there is more to data structures than arrays made up of strings. Below, I leave you with a little more information to expand your understanding. Things you may want to look at next to understand these concepts more comprehensively.
The first port of call to search for information for me is always MDN. It's one of the most reliable sources of information for developers.
- Data types: The data we worked with here was made up of
strings. But there are a few more types of data like
booleans(true or false) that you will need to understand.
- Requests: We briefly mentioned how usually we would make a request to our database to get the data we need to use. Working with APIs,
fetch(), making requests and handling the response is an advanced topic that you can safely leave for later. But one that’ll be essential by the time you are starting to interview for a developer job.
Thanks for reading. I hope you found this useful. And if you enjoyed it, sharing it around would be greatly appreciated.