Full Stack JavaScript Strategies

Chapter 3. Building the Data Schema

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 3rd chapter of the final book.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the author at [e-mail].

The data layer covers a lot, so it’s awesome that we have so many good tools to work with. Regardless of the tools you choose, you do need to understand what’s going on beneath the surface. When you start building your data schema, take your time to really write it out. The data schema drives everything for the app and any of its dependencies. Over time, it can become hard to update the schema without breaking everything.

Since you’ve already decided what kind of backend architecture to go with, you probably have an idea of how data will be related and what that data looks like. Making a diagram of how the data will be connected is going to help you and the team a lot because you’ll see the relationships.

That’s why this chapter is going to cover:

• Initial considerations for setting up the data schema

• Setting up a database

• Using object relational mapping (ORM) tools

• Writing data migrations in your database

• Seeding the database with initial data