Recommended approach serverless/cloud?

dbssd

last month

4

• 

  denolfe

  Payload Team

  last month

  Welcome @dbssd ! Glad you found us.

  
  
  

  There are trade-offs to each approach:

  
  
  

  1. Payload + Next.js, serverless on Vercel. This approach is great for lightweight apps that don't do a lot of heavy-lifting. The main downside here is that you'd need to account for cold-starts that are inherent with any serverless platform.

  
  
  

  2. Payload + Next.js deployed separately. This is typically the approach that we recommend as it offers greater flexibility in deployment platforms. The downside is like you said, you have to deal with 2 deployments.

  
  
  

  If I were starting a large, greenfield project with Payload and Next.js. Here's how I would do it:

  
  
  

  - Monorepo with 2 separate "apps": Payload, Next.js

  
  

  - Configure a

  payload-types

  package within the monorepo for Payload to compile the types to.

  
  
  

  This has the benefit of:

  
  
  

  - Unified git history and repo tooling

  
  

  - Shared types between frontend and backend

  
  

  - Can utilize deploying

  either project

  from the same repo as most deployment platforms let you set the src directory (if needed for your monorepo).

• 

  Panda

  last month

  is there anywhere an example for how to do the payload-types package within the monorepo? I currently just copy paste the types but if there's a way to skip that part I'd be glad

• 

  denolfe

  Payload Team

  last month

  It will vary between monorepos depending on what you use to manage it. However, they'll all have the concept of a "shared package", which is where you'll configure your payload script to output to

  
  

  
  

  I don't know of an example offhand