graphql-upload VS better-sqlite3

Uploading cloud storage (s3, firebase storage, etc) is probably best. I do not recommend it, but graphql-upload is a thing. https://github.com/jaydenseric/graphql-upload

Look at the grapqhl file upload spec (https://github.com/jaydenseric/graphql-upload). Basically the custom type File is just a string path which the server will use to get the file from the multipart request.

I am not sure if this actually a problem with graphql-upload or webpack or something else. I also noticed that my issue looks similar to this issue, but I didn't really understand if there were any fixes to that issue and if indeed it is the same issue I am facing.

For file-uploads there is https://github.com/jaydenseric/graphql-upload. Usually at scale you would use a service such as S3 for storing the files. IMHO, proxying the files through the GraphQL server is a big performance penalty. Therefore I would rather recommen uploading to the file storage directly from the client, e.g. by issuing a pre-singed upload url that can be requested via a GraphQL mutation.

To upload images with GraphQL, make sure to add [graphql-upload](https://github.com/jaydenseric/graphql-upload).

In the second video of the series, we are separating routers and adding SQLite, Better SQLite 3, Database to the application to show access to context for performing a simple query and mutation.

If I were charged with this task I'd probably take an actual SQLite DB and write methods to parse data from text files, then process it within SQLite, and serialize it back to the text file when an API method is called or after each processing step. A fresh DB engine, fully re-implemented to match SQLite's API is insane unless you're a prodigy or have a sizable team and will come with numerous downsides. I can recommend https://github.com/WiseLibs/better-sqlite3 and https://github.com/loveencounterflow/dbay

better-sqlite3 is orders of magnitude faster than the async SQLite bindings. We found this to be true when testing SQLite options for Notion's desktop app anyways.

https://github.com/WiseLibs/better-sqlite3#why-should-i-use-...

Better SQLite is a wrapper around the SQLite database engine that provides a number of improvements over the standard SQLite API. One of those benefits is type safety, Better SQLite uses TypeScript to provide type safety for queries, which can help to prevent errors.

better-sqlite3 does the job synchronously

I used better-sqlite3 . It is simple to use as it is synchronous. I don't know if it scales good (at least the docs say it) but works great for my small use cases.

Kent's recommended NodeJS module, `better-sqlite3`, has some very nifty features including the creation of JavaScript user-defined functions[0] that (if I understand this right) can be called from SQLite. Combined with TRIGGERs, I wonder if it might fire a function within the app when an UPDATE/INSERT happens from a different process? (This is me wondering out loud, I don't actually know.)

I also recommend checking out Replicache[1] and alternatives, which may be a better way to handle the networking and database replication so that it doesn't rely on the underlying DB.

[0] https://github.com/WiseLibs/better-sqlite3/blob/HEAD/docs/ap...