Introduction

Working With Monorepos

Workspaces

Shared Configs

Frontend

Schema

Backend

Introduction and Getting Started

Analyzing

Designing the Customer-facing UI with TailwindCSS

Data Model

Analysis and Design

PostgreSQL Ranges

The Provider Table

The Booking Table

Modelling with advanced Postgres features

Tailwind CSS

Foundation

Frontend State

Shared Components

Select Day

Frontend UI

Introducing tRPC

Connecting to tRPC

Refining the tRPC setup

Connecting to the Database

Generating Zod schemas

Endpoints

Testing tRPC Endpoints

Testing With the Database

Testing Frontend

Testing

Completing the Select Date Page

Infrastructure for Ranges

Completing Booking

Connecting The Dots

Conclusion and extra resources

This comprehensive course will equip you with the skills and knowledge to build modern full-stack applications using TypeScript, TailwindCSS, tRPC, and PostgreSQL. You will learn how to create a robust and scalable application architecture, from the backend data layer to the frontend UI.

PostgreSQL

NodeJS

Knex

React

TypeScript

tRPC

Monorepos simplify code development and can be split when necessary.

Setting up npm workspaces in our monorepo

Setting up shared Typescript, ESLint and Prettier configs

Master full-stack development with a single repository for everything!

Learn the art of full-stack development with this comprehensive course. Through implementing the latest technologies and techniques, the course directly addresses the most common challenges full-stack developers face:
- **Code consistency and sharing:** Monorepos eliminate the need for multiple repositories, ensuring consistent code across your application and facilitating seamless code sharing.
- **Technology integration:** Learn how to integrate modern technologies like TypeScript, Tailwind CSS, and tRPC, empowering you to build robust and maintainable applications.
- **Database management:** Master advanced PostgreSQL features to optimize data storage, retrieval, and manipulation, ensuring a high-performance and scalable backend.

Build type-safe full-stack applications with database-centric strategies

This comprehensive full-stack development course covers monorepos, TypeScript, Tailwind CSS, tRPC, and PostgreSQL, empowering you to build modern, scalable applications. Structured into 7 modules of bite-sized lessons, each module is designed to be engaging and informative, combining video lectures, hands-on coding exercises, and real-world examples.

Fullstack Typescript with TailwindCSS and tRPC Using Modern Features of PostgreSQL

Writing PostgreSQL ranges for the application database.

Breaking down the UI to build it with Tailwind CSS

Master monorepos for streamlined development workflows and enhanced collaboration

Implement TypeScript for type-safe code that prevents errors and improves maintainability

Utilize Tailwind CSS to create consistent and beautiful user interfaces

Employ tRPC for seamless data exchange between frontend and backend

Harness advanced PostgreSQL features for optimized data storage, retrieval, and manipulation

Build modern, scalable full-stack applications using a unified approach

That concludes the course! I hope it was useful to you and that you feel we've covered most of what you would need to make a web app from beginning to end.

Like I said in the intro, there are a few things I would have loved to cover that simply didn't make it.

In order to give an indication of what I would do, here is a short list of things that I would have covered:

It's becoming popular to use Auth0, Okta, AWS Cognito or one of the other services for Auth(entication/orization). I have refrained from those in my own projects so far because I like to keep dependencies on third party services to a minimum. There is a trend towards setting up architecture with complicated Terraform code and lots of little AWS services and the like which I don't enjoy. In my opinion, the ultimate developer experience is that where I can check a repository out and turn it on while disconnected from the internet and everything works. That is not always possible, but when it is it makes things significantly easier to work with, debug and to run CI on.

As you can probably tell, I am a big fan of PostgreSQL. It's a rock solid piece of software and can serve you really well in many ways. I often refer to this blog post: 

 by Stephan Schmidt. For instance, I often use 

 for queuing. It's great because you can start by simply running it in-process, adding no infrastructure overhead at all. When the time comes that you need to scale (which will be later than you think), you can move it to a separate process/service and it can continue to use the same database.

That said, security is becoming increasingly important with each passing year and for that reason, I might soon change my stance on authentication services. Similar to hosting an email server, it's something that you can do yourself, but it's becoming closer to a full time job because of the complexity.

If you still want to do it yourself, please read up on current knowledge. At this time it is my understanding that 

 is still the best way to encrypt tokens. Also, you should probably just send people an email with a login code or token rather than ask them to store a password, or even better, use 

---
title: Conclusion and extra resources
description: Conclusion and extra resources
isPublicLesson: true
privateVideoUrl: https://stream.mux.com/xhcmVeljro01NWYXhV300tt1HbyVhyE00aGmfRs1IbgvHk.m3u8
---

# Conclusion

That concludes the course! I hope it was useful to you and that you feel we've covered most of what you would need to make a web app from beginning to end.

Like I said in the intro, there are a few things I would have loved to cover that simply didn't make it.

In order to give an indication of what I would do, here is a short list of things that I would have covered:

# Auth and security

## Service or home made?

It's becoming popular to use Auth0, Okta, AWS Cognito or one of the other services for Auth(entication/orization). I have refrained from those in my own projects so far because I like to keep dependencies on third party services to a minimum. There is a trend towards setting up architecture with complicated Terraform code and lots of little AWS services and the like which I don't enjoy. In my opinion, the ultimate developer experience is that where I can check a repository out and turn it on while disconnected from the internet and everything works. That is not always possible, but when it is it makes things significantly easier to work with, debug and to run CI on.

As you can probably tell, I am a big fan of PostgreSQL. It's a rock solid piece of software and can serve you really well in many ways. I often refer to this blog post: [Just use Postgres for Everything](https://www.amazingcto.com/postgres-for-everything/) by Stephan Schmidt. For instance, I often use [graphile-worker](https://github.com/graphile/worker) for queuing. It's great because you can start by simply running it in-process, adding no infrastructure overhead at all. When the time comes that you need to scale (which will be later than you think), you can move it to a separate process/service and it can continue to use the same database.

That said, security is becoming increasingly important with each passing year and for that reason, I might soon change my stance on authentication services. Similar to hosting an email server, it's something that you can do yourself, but it's becoming closer to a full time job because of the complexity.

If you still want to do it yourself, please read up on current knowledge. At this time it is my understanding that `bcrypt` is still the best way to encrypt tokens. Also, you should probably just send people an email with a login code or token rather than ask them to store a password, or even better, use [webauthn](https://webauthn.guide/).

## Internally

Once you have a token, I would store is as a JWT in localstorage or as a cookie, send it in the header with every tRPC request. Refer to the [docs](https://trpc.io/docs/server/authorization) for details on how to do this. I typically create a procedure type for the various authorization types (user, admin, etc.) -- see the [docs](https://trpc.io/docs/server/middlewares) about this as well.

Learn

The newline Guide to Building Your First GraphQL Server with Node and TypeScript

Teach

Amelia Wattenberger

Author of Fullstack D3

Community

Fullstack Typescript with TailwindCSS and tRPC Using Modern Features of PostgreSQL

Module 1: Introduction and Getting Started

Introduction:

Start Here

Lesson 1: (3:09)

Introduction

Lesson 2: (6:35)

Working With Monorepos

Lesson 3: (6:45)

Workspaces

Lesson 4: (17:56)

Shared Configs

Lesson 5: (9:27)

Frontend

Lesson 6: (16:20)

Schema

Lesson 7: (5:21)

Backend

Module 2: Analysis and Design

Lesson 1: (3:09)

Analyzing

Lesson 2: (4:04)

Designing the Customer-facing UI with TailwindCSS

Lesson 3: (2:49)

Data Model

Module 3: Modelling with advanced Postgres features

Lesson 1: (6:18)

PostgreSQL Ranges

Lesson 2: (16:10)

The Provider Table

Lesson 3: (4:47)

The Booking Table

Module 4: Frontend UI

Lesson 1: (1:25)

Tailwind CSS

Lesson 2: (7:58)

Foundation

Lesson 3: (21:53)

Frontend State

Lesson 4: (4:52)

Shared Components

Lesson 5: (16:13)

Select Day

Module 5: Endpoints

Lesson 1: (7:45)

Introducing tRPC

Lesson 2: (17:22)

Connecting to tRPC

Lesson 3: (7:22)

Refining the tRPC setup

Lesson 4: (7:28)

Connecting to the Database

Lesson 5: (4:56)

Generating Zod schemas

Module 6: Testing

Lesson 1: (4:33)

Testing tRPC Endpoints

Lesson 2: (25:00)

Testing With the Database

Lesson 3: (12:37)

Testing Frontend

Module 7: Connecting The Dots

Lesson 1: (21:07)

Completing the Select Date Page

Lesson 2: (14:07)

Infrastructure for Ranges

Lesson 3: (15:49)

Completing Booking

Module 8: Conclusion and extra resources

Lesson 1: (1:02)

Conclusion and extra resources

Conclusion and extra resources