Angular Beyond the Front End

Ryan Chenkie

@ryanchenkie

Google Developer Expert

JavaScript Consultant

Angular / React / Node / GraphQL

How do you choose a backend?

The "Full Stack" Developer

How can we be better full-stack developers?

Expanding Angular's Capabilities

Front End

Backend

✓ 

Modules

Components

Dependency Injection

Services

Routing

 

✓ 

✓ 

✓ 

✓ 

x

Modules

Components

Dependency Injection

Services

Routing

 

x

x

x

x

Nest Gives Us Angular on the Backend

Front End

Backend

✓ 

Modules

Components

Dependency Injection

Services

Routing

 

✓ 

✓ 

✓ 

✓ 

✓ 

Modules

Controllers

Dependency Injection

Services

Routing

 

✓ 

✓ 

✓ 

✓ 

Why Angular?

  • Opinionated
  • Prescriptive
  • Guided
  • Supportive

In General

  • TypeScript by default
  • CLI
  • Standard way of doing almost everything

Tech-Specific

Nest carries over the general and technical thing we like about Angular

Nest knows about the things we might need and is prescriptive about how to acheive them, while still be flexible.

Common Server Needs

  • Delay app start - Async providers
  • Middleware - NestMiddleware
  • Communicating with databases
  • ORMs

DEMO

How do I adopt Nest gradually?

Existing Node App

  • HttpAdapter (for express or Fastify)
  • Extract business logic and put Nest on top

Existing Something Else

  • Reverse Proxy and slow migration

Who is Using Nest?

Slides

bit.ly/nestjs-angular

@speakdotdev

graphcollective.io

@graphcollective

Thanks!

Ryan Chenkie

@ryanchenkie

Made with Slides.com