Full Stack JavaScript Strategies

Chapter 2. Setting Up the Backend

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 2nd 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].

You’ve got all your tickets ready to go, and you can assume you’ve been tasked with building the bones of the backend. The framework of choice at your company is NestJS. It’s OK if you’ve never seen NestJS or even heard of it before. The docs for it are good, and you’ll have other code you can reference. Reach out to other developers to see why certain architecture and design decisions have been made on existing backends.

In this chapter, you’ll learn about:

• Making architecture decisions for the backend

• Checking the app to make sure it runs after initial setup

• Writing the initial documentation

These tasks are all crucial to ensuring that development is able to run smoothly as both the Product and the dev team grow and change over time. Everything that you build on the backend will start from the foundation you set here, so take your time to thoroughly discuss options with your team.

Why NestJS?

Before we dive too deep into the weeds, let’s discuss ...