Build a UGC Live Streaming App with Amazon IVS: Creating a User (Lesson 2.1)

In lesson 1, we learned all about StreamCat - a UGC live streaming application. We learned that StreamCat uses AdonisJS, and AlpineJS, and learned about the application schema and architecture. In lesson 2, we'll focus on what happens when new users register for an account.

As a reminder, there are two categories of AWS resources that make up the cloud architecture of the StreamCat application. The first category is a set of pre-built resources - things like the Amazon RDS PostgreSQL instance, Amazon EventBridge rules, and AWS Lambda functions that handle automated chat moderation and persistence of live stream events. These pre-built resources were deployed to the AWS cloud via the AWS Cloud Development Kit (CDK). The second category of resources are created and deployed on-demand. This group of resources include an Amazon IVS channel, chat room, and stage (for multi-host, real time live streams). The Channel, ChatRoom, and Stage resources all have a one-to-one relationship with a User, as illustrated in the following diagram.

When a new user registers for a StreamCat account, the application will create and persist a new User entity.

The username and password are sent to a /register endpoint via an HTTP form POST. These values are used to create a new User and persist that User to the database.

Once the User is created, we can now focus on creating the Channel, ChatRoom, and Stage entities via the AWS SDK for JavaScript (v3). In the StreamCat application, the functionality for working with each entity is encapsulated in a reusable service class, respectively named ChannelService, ChatRoomService, and RealTimeService (for working with Stage entities).

In this lesson, we learned how the StreamCat application creates a new user and what resources need to be created to enable broadcasting and playback for that user's live stream. In the next lesson, we'll look at how to create an Amazon IVS channel for each user.