studio VS serverless-websockets

Use AsyncAPI Studio to validate the written specification.

Async API Studio - browser based tool that validates and renders the spec on the fly

Dev effort in our react component in the 1.0 version so that we can start working on Studio UI.

For long running jobs, it is useful to inform the user that something is going on. Nobody likes sitting and waiting hoping that work is being done. To help with this, we provide push notifications via the WebSocket microservice we created in my WebSocket tutorial.

For a real world example, you can check out my repo on AWS WebSockets.

There are two things you must do before configuring a custom domain: purchase your domain name and setup a public hosted zone. These will need to be done manually in order to pick up and deploy the stack contained in part five of the GitHub repo for the WebSocket.

Just like the three previous parts, the work is done ahead of time. To deploy the updates that add user notifications, run the following command in a terminal in the root of the repo on your local machine.

To get started with the spec for our WebSocket, checkout the part-three branch in the serverless-websockets repo in GitHub with the following command:

If you followed part one of this series, you deployed a basic WebSocket into your AWS account. It has the ability to add and remove connections, as well as add and remove subscriptions to specific entities. Today we are going to use a branch in that repo that enhances what we had.

Today we're going to go through an example of a WebSocket written in a SAM template. I chose a SAM template because of how easy it is to deploy a serverless application directly into AWS without the need for 3rd party services.