Building data-driven web apps with Pyramid and SQLAlchemy Transcripts
Chapter: MongoDB edition
Lecture: Introduction to the NoSQL version

Learn more about this course
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 our PyPI demo app
0:11 this time with a NoSQL-based document database
0:16 called MongoDB.
0:17 It's the most popular of the document databases
0:19 but the ideas will be pretty similar across the board.
0:23 So the first question is, 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 many people prefer document databases
0:32 over relational databases.
0:34 The whole thing about migrations?
0:35 A whole lot less of that
0:36 when you're doing document databases and things like that.
0:39 The running of it 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 is we've talked a lot about
0:50 some amazing design patterns.
0:52 We've organized our code in nice ways.
0:54 We have these data access services
0:56 that group say the user queries
0:59 and data processing, 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 takeaway here is the power of these design patterns
1:09 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 and actually completely switch
1:17 not just the database
1:18 but entirely the style of underlying data altogether.
1:22 So it's going to be really quite easy and quite awesome.
1:26 If you're not interested in MongoDB
1:27 feel free to skip to the end.
1:29 Skip over this chapter.
1:30 But if you are or you want to see the power
1:32 of these design patterns 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.