Building Data-Driven Web Apps with Flask and SQLAlchemy Transcripts
Chapter: MongoDB edition
Lecture: Introduction to the NoSQL version

Login or purchase this course to watch this video and the rest of the course contents.
0:00 We've built our app.
0:01 We've deployed it. It's basically done.
0:03 But let's take one more look.
0:05 Let's try one more version of our application.
0:08 So we're going to rebuild
0:10 our PyPI demo app this time with a
0:13 NoSQL based document database called MongoDB.
0:17 It's the most popular of the document databases
0:19 but the idea is it'll be
0:20 pretty similar across the board.
0:23 So the first question is
0:24 why are we doing this?
0:25 Why do we have this MongoDB version?
0:26 Well, there's two basic reasons.
0:28 The first reason is
0:30 many people prefer document databases
0:32 over relational databases.
0:33 The whole thing about migrations
0:35 whole lot less of that when you're doing document databases
0:38 and things like that. The running of it
0:40 is easier a lot of times.
0:42 And also the performance can be better.
0:44 So that's one reason.
0:45 People might just want a MongoDB version.
0:47 The other reason though
0:48 is we've talked a lot about
0:50 some amazing design patters.
0:52 We've organized our code in really nice ways.
0:54 We have these data access services that group
0:57 say the user queries and data processing,
1:00 the package processing,
1:02 and we have our view models.
1:04 So what I'd like to show you
1:05 the main take away here is the power
1:08 of these design patters that we've employed.
1:11 What you'll see is we'll be able to change
1:12 a very few set of files
1:15 and actually completely switch not just the database
1:18 but entirely the style of underlying data all together.
1:22 So, it's going to be really quite easy
1:25 and quite awesome.
1:26 If you're not interested in MongoDB
1:27 feel free to skip to the end. Skip over this chapter
1:30 but if you are or you want to see the power of these design patters
1:32 to allow us to evolve our application as we build it
1:36 so we don't have to design it all perfectly up front
1:38 'cause you never do,
1:39 you'll get to see that in action during this chapter.