relay-starter-kit VS bree

https://github.com/kriasoft/react-starter-kit (or, relay-starter-kit)

GitHub

It also helps to have a REPL shell for Knex.js — https://i.imgur.com/P5bVdoC.gif

I generate TypeScript enums and types from the actual database schema using knex-types as part of the yarn db:reset script that used during local development (after making changes to the db schema migration files). See example project.

I tried to take advantage of TypeORM in a couple of projects, but then reverted back to knex + knex-types — just a PostgreSQL client with query builder works great, IMO, especially for GraphQL API development.

GraphQL API and Relay Starter Kit— an example of implementing GraphQL API optimized for the serverless environment (Google Cloud Functions) + a reverse proxy using Cloudflare Workers

It helps to have a monorepo setup with packages/projects such as "api", "worker" (cron job) etc. all consuming the same environment variables (db connection settings etc.), when the cron job "serverless" function is deployed, it just picks the required environment variables from the shared "env" folder/package.

If you only need a single instance, you can use Bree to handle your cron jobs without blocking your main thread.

Been using https://github.com/hexagon/croner and https://github.com/breejs/bree depending on the use case, both are currently being maintained.

Bree is another package with support for workers threads and cron syntax. But for the purpose of this article, we will stick to node-cron. So let's run a simple example:

For more advanced use cases, you might want to look into using a full-featured job queue instead like bree, bull, or agenda.

An impressive scheduling package I use is called Bree: https://github.com/breejs/bree

Bree is a super cool cron like scheduler that uses workers to run jobs https://github.com/breejs/bree