How to Create a multi-user Chatroom Hosted on Serverless Cloud?
In this tutorial, you’ll learn how to create a multi-user chatroom that is hosted in the cloud. I’ll describe how to create the front-end (the UI) and how to implement the back-end (API and implementation), and how to make all the code live on the web. By the end of the tutorial, you’ll have a URL that you can share with others to use your chatroom.
Instead, you will write your front-end and back-end logic, enter one command on your terminal and like magic, you will get a dedicated URL that serves your UI from a CDN from a domain name that is yours and secured by SSL. Your backend logic will run on demand as visitors use your chatroom. It will scale as more users enter your chatroom, and it will cost you almost nothing to run. What is this magic I speak of? This is Serverless Computing and it will change the way you develop cloud applications, forever.
Before you start to think this is too good to be true, let’s begin and if you aren’t a believer by the time you’re done, we will send you a t-shirt. Well, we’ll send you a t-shirt anyway for trying this tutorial out, but we’d love to know that when you go from code to cloud in 30 seconds, you’re a serverless convert and will share this joy with others. At Nimbella, our goal is to demystify the cloud and make it accessible to everyone - all developers with diverse skill sets and backgrounds. Let's start building.
Here's your roadmap for the rest of the tutorial.
- Nimbella CLI: your tool to the cloud
- Chatroom architecture
- Project organization
- The Chat UI (frontend)
- Serverless API Implementation (backend)
- Code to Cloud in 30 Seconds
1. Nimbella CLI: your tool to the cloud
The Nimbella CLI is called "nim". It helps you organize and deploy your serverless applications to the Nimbella cloud, to a secure domain that is unique to your projects. You will need to download the CLI and login with an access key to get started. Please visit the signup page to sign up and learn how to configure your CLI if you haven't previously done this.
2. Chatroom architecture for Serverless Chat App
The following diagram illustrates how the Chatroom UI (frontend) interacts with APIs on the backend.
The APIs allow the frontend to complete the following essential actions:
- Create a new user
- Get all users
- Post a new message
- Get all messages
Each of these actions occurs when users interact with the UI. The APIs can store or retrieve information from a Key-Value cache included with every Nimbella account so you can build stateful serverless applications out of the box. After completing whatever task the API is assigned, it provides information back to the UI which displays it to the user.
3. Project organization
There are three steps to build and deploying an application (e.g., frontend + backend) to Nimbella:
nim project deploy /path/to/project
- using the CLI to deploy your local project to the cloud. At this point your serverless application is live on the web, with a dedicated domain name assigned to your project and a signed SSL certificate for secure communication.
BONUS Resource: There is extensive documentation for configuration and deploying your projects to Nimbella for later reading.
4. The Chat UI (frontend)
Our chatroom uses React to create a UI that responds to data from our APIs. You will find the implementation on GitHub. The React code is located inside the web folder and calls the APIs we will create below. For more details about adding web content to your project, you'll want to read the relevant parts of the CLI documentation. For now, it suffices to know the contents must exist in a "web" folder after the React build completes. By using React, we can develop and test the frontend locally for faster iteration.
5. Serverless API Implementation (backend)
In a standard chatroom, there are two types of data that we transfer, the user and the message. Each message has some user data, so let's create a system to store and access users. I'm also going to go over all the other backend actions and explain how they work.
Create a User:
To start our collection of chat APIs, let’s create a user. In order to do that, we need to retrieve the paramters which will be the username, validate the username, and add the username to the cache provided within your namespace.
You'd want your users to know who is apart of this message board. So we run a command that instantly goes through the cache of users and displays them.
In order to display all the messages in the order they've been given, we just push them to the end of the cache.
After sending a message, let’s build an API that retrieves messages. Include logic to page through messages if important to your use case. We parse and return the messages it provides.
Lets say one of your users sends a messages but they end up regretting it. You'd want your users to easily be able to remove any mistakes they posted. That's where the delMessage command comes in. After simply clicking the "X" button next to the post you want to remove, the code will go into Redis, find the key-value of that message, and remove it from the cache.
So you created an account but for whatever reason, you don't want to be apart of this message board anymore. That's where the DelByUserId function comes in. You have the ability to remove yourself from the list of users on the board.
So you're the admin on the message board and for whatever reason you want to remove all the users who are apart of your chat. You have three options.\
- Delete the entire website and start from scratch.
- Delete them all one at a time. Which isn't bad if there's only a handful of users, but an absolute nightmare if you had thousands of users.
- Run the delAllUsers command.
Personally, I'd go with the third option. In this command, we confirm that you are indeed the admin of this board. The last thing you'd want on a message board is for everyone to have access to a command that would remove all the users. It goes into Redis and uses the key-value store to select each user one at a time and removes all of them.
6. Code to cloud in 30 seconds.
The Nimbella CLI is called
nim . It helps you organize and deploy your applications to the Nimbella cloud, in a secure domain that is unique to your projects. You will need to download the CLI and login with an access key to get started. Please visit the signup page to configure your CLI if you haven't previously done this. As described earlier, deploying your functionality and UI is incredibly simple with the following line of code.
nim project:deploy <project_name>
Within seconds, Nimbella will tell you how many files and actions they hosted. Navigate to the link provided by Nimbella after running the command to access your finished Serverless Chat app.
This tutorial detailed the steps involved in creating an Serverless Chat application using the Nimbella Platform.
Nimbella is evolving and expanding. Check out Nimbella's website for more information on our upcoming products and news. Contact us at email@example.com or on our community Slack if you have any further questions. You can also check out the Chat app source code on GitHub.
- How to optimize Kubernetes costs with Nimbella
- Step by step guide on how to port from AWS to Nimbella
- How to build and improve your serverless APIs
- Simplifying Kubernetes For Developers
- FaaS Wars Season 2 - Step By Step Instructions
- What is Nimbella and what does it offer?
- Results and Feedback of FaaS Wars - May the FaaS Be with You!
- 28 Serverless Gurus and experts One Must Follow in 2021
- The Faas Wars Alert!
- CI/CD pipeline with GitHub Actions
- How to deploy Node.js functions on Nimbella
- Kick-Start Your Serverless Journey
- AWS re:Invent Serverless Highlights
- Opportunities in the Wake of the AWS Juggernaut
- FaaS Wars: Serverless & Virtual Robot Competition
- #DeveloperIPL Online Hackathon Results & Feedback on Nimbella's Integration for Postman
- How to connect to the 3rd party database such as MySQL at Nimbella (example in Java)
- What can you do with the Nimbella Workbench?
- Deploy your Shopify Storefront to Nimbella
- Not All Serverless Platforms Are Created Equal
- Nimbella + Netlify: Uplevel Your Development Speed
- How we learned to Jamstack, Our Caputron Story.
- Commander for Microsoft Teams - Your Custom Bot that runs on your Command!
- How to Build a Stateful Cloud App on Nimbella vs. AWS
- Starter Kit and Resources to Build a Serverless Cloud Application
- How to Build Serverless Slack Apps and Commands
- How to Set up your Serverless Environment and Get Started in Less than 2 Minutes!
- How to Quickly Deploy Stateful Serverless Apps with Nimbella?
- What is Serverless Computing? 3 reasons to start now
- How to Build a Serverless Slack App in Minutes.
- How to Manage your Netlify Website from Slack?
- How to Build a Serverless Slack Command in minutes
- How to Build a Stateful Serverless Cloud Web Application?
- How to Create an Optical Character Recognition (OCR) Application?
- Development at the Speed of Innovation – Nimbella, the Serverless Cloud
- Software Security Features on Enterprise Serverless Slack Apps Enabled by Nimbella Commander
- Coronathon India’s first demo day has 18 projects to help fight COVID-19
- See the time in different cities on Slack with Nimbella Commander
- Greet your friends in their native language in Slack with Nimbella Commander
- Install Commander on your Mattermost Instance
- How to Fetch your Digital Ocean Billing Info on Slack?
- How to Stay Updated with Coronavirus Statistics on Slack?
- Create BlueJeans meetings on Mattermost using Commander
- How to Fetch your AWS Billing Info on Slack?
- Get your Datadog billing info in Slack with Nimbella Commander
- Serverless Slack Apps and Slash Commands
- How to use Slack Effectively with Nimbella Commander?
- How to Create a multi-user Chatroom Hosted on Serverless Cloud?
- Using Docker actions, running Golang, and other fun things with OpenWhisk
- The duality between serverless functions and APIs
- Serverless HTTP handlers with OpenWhisk
- Serverless functions in your favorite language with OpenWhisk
- Run Swiftly: precompiled Swift actions
- Performance debugging for serverless functions using the Cloud Shell
- Locally debugging OpenWhisk actions
- Composing functions into applications
- A Serverless Composition of Functions
- The Serverless Contract
- The dawn of the Cloud Computer
- Security and Serverless Functions