Results for tag "sql"

4 Articles

SQL vs NoSQL. Part Three.

In previous posts I talked about SQL and NoSQL, and I want to go into a little more detail (while keeping it simple) what makes them different.

Scalability>>> Think making big things small. In SQL data is stored vertically (so typically all on one server- expensive!).  NoSQL stores it horizontally (many servers==ok).

Schema>>> Technically schema means a representation of some model. In programming land, it is used to refer to a structure of a database.  So think because you can’t see a database (at least I hope you can’t) you have to think how that structure is represented.   In SQL, the schema is fixed, columns must be decided ahead of time, and you have to put data in every column.  Remember that wine shelf? You can’t really be adding a new column to your shelf after you’ve built it…it will probably look like all the images when you google “shelf fail.”

Shelf Fail

I don’t know why, but this shelf is kind of cute.

Also, you have to put a bottle in every slot. Someone’s going to be a happy wine collector.

NoSQL deals with schema in a very different way. It just says “Nope.” and walks away. You can add (or leave out) anything you want, anytime you want. Now that’s flexibility.

Data>>> Finally let’s get to the data. In SQL all rows contain one specific entry. For example, in a row containing information about a bottle of wine you might have “Year”,”Location”,”Winery” etc. You can’t have two years for a bottle of wine, or two locations. In NoSQL, that’s A-OK. You can have two wineries (maybe it was a collaboration?) or no wineries. If that’s what you want.

More reading.

Next post I’ll be going into more detail about NoSQL and specifically MongoDB.



What follows a really bad movie about databases?


This is SQL.
wine bottles

This is NoSQL.
wine bottles pile

As discussed in my previous post- SQL is a relational (tabular) database, one that looks like an Excel sheet or an empty shelf. NoSQL is its evil twin sister.

The lovable evil twin sister.

People like NoSQL for it’s flexibility. You can only fit one wine bottle per shelf using SQL, but with NoSQL you can throw those wine bottles in a pile and it’s A-OK.

Also some people believe it is faster… but there are a lot of mixed opinions on this…

Let’s look for our favorite red wine again…

db.shelf.find( { “taste”: “delicious”, “dryness”: “dry” , “color”: “red”} )

A lot shorter, isn’t it?
You find your wine not by searching for it in it’s proper cubby in its designated row and column, you search by keys.

As you can imagine, there are pros and cons to this. A lot of companies are still reluctant to embrace NoSQL. (See other article)

Here’s some more reading. If you have some time to kill.

Take care out there. There’s wild Pokemon.

DIR: 07/04 Happy Monday

Day In Review: What I checked out today so you don’t have to

Unless you want to.

This section of the blog will be for posting some articles that I read everyday, and my honest opinion of whether they are worth your time or not. To save articles across the web, I use a combination of Pocket (more for long term saves) and Degreed (for something I will read later that day.

So let’s get to it:


Today I stumbled across this article on Twitter today, and it caught my attention because both Spark and R are things on my “To Learn” list. I like the “Seven Steps” approach (only seven steps can’t be that hard right?) because it makes it seem more manageable. It is concise, contains a lot of different links (plus links to videos and reading) and is honest about what skills you will get in these seven steps. Good to get you started and head you in the right direction.

Rating: ★★★★☆


An article that spawned the idea for the SQL and noSQL posts. The bold headings make for an easy read, and it’s quite concise.


Rating: ★★★☆☆

Stock Photography

And here’s for our random pick of the day. I was looking for pictures to accompany blog posts and I stumbled across this gem. Specifically Unsplash, which is one of the sights mentioned. Searchable, and beautiful, free pictures. Because, let’s face it; everything free is beautiful.

Rating: ★★★★★

Thanks for the read.

What follows a movie about databases?

the SQL.

…I don’t get it.

It’s pronounced SEE-QUILL. Like “sequel.”

And it is…

a database.

Well…I vaguely understand what that means, but I’m a visual person.

Ok. I got it.

A database is like an empty shelf. We’re going to go with a wine shelf. Because people like wine.

I don’t.

Well, that’s good for you. Anyway you use a shelf to store things until you need them. A database works the same way. There are different types of databases, and SQL is a relational database management system. Which means it looks like a Excel chart. Or an empty shelf.

empty wine shelf

How am I supposed to remember that?

Just remember an empty shelf is what you’ll have when your relations come over and drink all your wine. As with any wine shelf, you can only fit one bottle of wine in any given space.

wine bottles

Unless you have bottles of ice wine. In that case you are very lucky.

SQL databases work the same way. You have one piece of data in each slot, and to find them you will use a key, or search by column or row. Here is how you would get a delicious red wine from our “shelf” database:

SELECT wine FROM shelf
WHERE taste = “delicious”
AND dryness = “dry”
AND color = “red”;

As you can see, it’s pretty easy to understand. If only we could search for our favorite bottle of wine in real-life as easily…

So why should I care?

Despite the fact that NoSQL databases (another type we will get to later) are rising in popularity- SQL still reigns. 79 percent of databases are relational databases. So next time you upload some cat photos or sign up for that website you know you will never use, think about where that data is going.

You have my attention.

If you are interested in learning more about SQL or *gasp* actually learning it, here’s a tutorial. And have fun uploading those cat photos.

Thank you.