graphql-ws VS better-sqlite3

There is already a JavaScript implementation for server + client with support for multiplexing from the same maintainer of graphql-ws: graphql-sse

Actually WebSocket is not the only protocol for executing GraphQL subscriptions. There is also a graphql-over-sse protocol, which is much more lightweight, and uses Server Sent Events. A popular implementation of it is the graphql-sse library, which is maintained by the same person as graphql-ws. The setup and API of both libraries is pretty similar.

That said, I feel so close to success that I can't quite give up. I am using graphql-ws as I understand this to be the new standard implementation of GraphQL Subscriptions. However, of course, Apollo subscriptions have not been updated to implement this. So, looking at the Recipes over on the graphql-ws documentation I have found the guide for using Apollo client. However as I am new to Apollo, it is using a lot of terms I am unfamiliar with.

Okay but seriously, if you've fallen down the rabbit hole of Apollo docs pointing you towards one library (subscription-transport-ws) which then points you to another (graphql-ws) , and so on and so forth, then hopefully this helps pull you out.

The most common protocol used today for subscriptions is the Apollo websocket protocol.

GraphQL subscriptions are just web sockets. You can check graphql-ws package if you want something without Apollo dependency. Though I don't understand why you want to not depend on it in the first place.

New GraphQL-WS ✔️

The interesting thing is that we can use any transport for delivering the results to client. The most popular implementation (as mentioned before) is subscriptions-transport-ws. Unfortunately, since it is poorly maintained, the GraphQL Working Group came up with a new implementation over WebSockets, graphql-ws.

Okay, so, how do I use WebSockets to add support for the GraphQL subscription operation? Doing a basic Google search, you’d be faced with a single solution, namely subscriptions-transport-ws. Looking through the repository, checking recent comments, reading through the issues and open PRs - might have you notice the abundance of bugs and their security implications. A summary can be found here.

Have you thought about using graphql-ws instead? It uses the new graphql-transport-ws protocol which also has an open RFC that is discussed in the GraphQL working Groups.

Best option for SQlite with node is this.

https://github.com/JoshuaWise/better-sqlite3

He's all over the issues section, and seems very knowledgeable about how SQLite works.

better-sqlite3 - The fastest and simplest library for SQLite3 in Node.js

I have searched the internet to the best of my ability but I'm unable to get it to work. I know there's an extension out there for it but I wanna know how to do it myself, to better understand the process. I found [this tutorial talking about amalgamation](https://github.com/JoshuaWise/better-sqlite3/blob/v5.0.1/docs/compilation.md). it's too vague for me to understand but I have a hunch that's the starting point

Most JavaScript libraries for SQLite3 don't support TRUE and FALSE keywords and they require you to prepare the statements in your code using integers. For example, in better-sqlite3 you would have to do this:

When I worked as an employee I contributed mostly just with docs fixes or bug reports (and not that often). I think it's mostly a mindset of seeing an issue yourself and noticing that others probably also are confused or misled by something so you go and report it!

Now that I'm working full-time on open-source and my own company I can contribute more easily to projects like upgrading SQLite source in a few bindings libraries [0], [1], [2] when 3.38 came out.

If anyone is interested in contributing to open-source and wants a bit more guidance though I have a number of good "first timer" projects related to data tools. Only expectation is that you have some experience with Go. Join discord.multiprocess.io, go to the #dev channel and say hi!

[0] https://github.com/mattn/go-sqlite3/pull/1019

[1] https://github.com/mapbox/node-sqlite3/pull/1550

[2] https://github.com/JoshuaWise/better-sqlite3/pull/778

Yes it's possible. I've used, for example, the better-sqlite3 library, which is written in C++, in an Electron app. React in the Renderer process would call Main process over IPC, then Main would use the Node bindings to whatever native Node module you're using.

better-sqlite3: another sqlite3 library in nodejs, works with recent versions of node and electron, uses node-gyp

Try this https://github.com/JoshuaWise/better-sqlite3

you can write your own table-valued, aggregate and window functions when you use better-sqlite3 (see https://github.com/JoshuaWise/better-sqlite3/blob/master/doc... see Database#function(), Database#aggregate(), Database#table()) in JavaScript.