bluelibs VS relay-starter-kit

We will be launching a new eCommerce solution based on our existing framework (www.bluelibs.com), we plan of having an Open-Core and the rest of the modules in a marketplace. And also do custom work for our clients that have very specific needs which Shopify' and others don't satisfy. I am asking for some feedback and inputs from people in the industry.

Suggestions, opinions, critiques are always welcome, hope I sparked your interest in this wonderful database. If you want to see what're we doing, you can "Watch" the monorepo.

www.bluelibs.com check this out :)

If you enjoyed this short article or library, please consider sharing the love with a star on GitHub!

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.