Series: WS + API: A NodeJS Server

I've got nothing else to talk about right now, so how about a series of posts about this web socket and API endpoint server I'm rewriting for the nth time?

I suppose the best way to get started when talking about a development project is to discuss the requirements, setup, and goals. I briefly covered the goals in the first post so I won’t go in-depth here but I will talk about…

Ever server needs a starting point, although this one doesn't do much on its own.

Before we continue with code, I wanted to stop off and talk at a very high level about HTTP and WS, and what each protocol means to me from a purpose standpoint.

Our main entry point sets up our combined HTTP(S) and WS server, but attempting to communicate with the server using either protocol will result in no response. In this post, we’re going to look at the middleware that allows the server to…

Now we're getting somewhere: dynamically handling messages from the client.

Before we move to the next part of the WS + API Server series, I wanted to talk a bit about Redis and Redis-OM.

Here's an example of using the web socket server to handle messages and store the results in Redis. Since I wrote this, modifications have been considered, but that's a post for another day.