Skip to content

Extensive MongoDB Realm tutorial to explore serverless functions.

Notifications You must be signed in to change notification settings

LucasHazardous/SentenceFusion

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

11 Commits
 
 
 
 
 
 

Repository files navigation

Exploring MongoDB App Services

Warning! This tutorial will involve serverless functions, Atlas Realm and making an exciting project.


Introduction

  • What are serverless functions?

    Serverless functions, also known as Function as a Service (FaaS), are a type of cloud computing service that allows developers to run and execute code without the need to manage or provision servers. In a traditional server-based model, developers have to set up and manage servers to host their applications and handle incoming requests. With serverless functions, developers can focus solely on writing and deploying code without worrying about the underlying infrastructure.

    Benefits:

    • No infrastructure necessary - in a serverless architecture, the cloud provider takes care of managing the servers
    • Pay for exact usage - billing is typically based on the actual execution time and resource usage
    • Autoscaling - the serverless platform automatically scales up the necessary resources to handle the incoming request
    • Multiple triggers - functions are triggered by events, such as HTTP requests, database updates, file uploads, timers, or messages from queues
  • What is MongoDB Atlas Realm?

    MongoDB Atlas Realm is a cloud-based serverless platform provided by MongoDB. It is designed to simplify the development and deployment of real-time applications that require data synchronization and event-driven workflows.

    Key features:

    • Real-Time Data Sync
    • Authentication and User Management
    • Serverless Functions
    • Integration with MongoDB Atlas
    • GraphQL API
    • Multiple SDKs

Mission

Assist in creation of a dynamic user-driven experience where players can unleash their creativity and shape an epic tale. But wait, there's a thrilling twist! Adhering to the golden rule, no solo consecutive sentences allowed! Brace yourself for an adventure where collaboration reigns supreme, ensuring that at least two courageous souls unite to craft an extraordinary narrative.

Our objective? The mighty MongoDB Realm configuration. Sharpen your skills, summon your determination, and let's embark on this exhilarating journey together!


Project - part 1

Setup

If it's your first time working with Atlas, go to Atlas login page. You can quickly connect with eiter Google or Github account. Then create a new project named SentenceFusion. Next you should have something similar to this:

empty project

Click Build a Database. Now you will have to select cluster configuration. Select whatever's free, for the region choose something close to your location.

cluster

Now you will have to create a user. We will use it later to log into Compass. Don't worry if you forget the password, you can reset it at any time. For the IP Access List remove your current address and add 0.0.0.0/0 to allow access from anywhere.

access

When you Cluster finishes creating click Browse Collections, then Add My Own Data. For the Database name enter fusion and for the Collection name enter sentence. Click Create.

create database

Authentication

Head to the App Services tab on the upper panel. Choose Build your own App.

create app

We will begin by adding user Email/Password authentication configuration.

authentication

authentication configuration

For now users won't be able to reset their passwords but a reset function must exist. We will go with the default password reset function, without any changes.

reset password function

When you are done click Save draft button at the bottom. When you do changes won't be instantly deployed until you click Review draft & deploy button, then you get a chance to review all changes and deploy them.

enabled authentication

Serverless Function

Let's create a function that will be used in a rule later. This function will be responsible for determining if a user can insert a new document.

Enter function list view from the left side panel. You should see resetFunc created earlier. Click Create New Function.

function list

In the Settings tab begin configuration:

function configuration

Authentication System will allow the function to execute with full priviliges and setting it to private will make it unreachable for regular users. We configure it that way because the only user of this function will be our rule. Log Function Arguments can be useful for debugging.

Now set head to Function Editor and write the following code:

exports = async function(arg){
  const mongodb = context.services.get("mongodb-atlas");
  const db = mongodb.db("fusion");
  const coll = db.collection("sentence");
  
  const latestDocument = await coll.find().sort({_id: -1}).limit(1).toArray();
  if(latestDocument.length == 0) return true;

  return latestDocument[0].userId != arg;
};

function code

Remember to save draft changes.

Rule

Now let's configure our rule. Go to Rules view on the left side panel.

role

Select sentence collection, then click blue Skip (start from scratch) text to create a fully customized rule. Fill settings with this configuration.

role configuration

In the Apply When you can place any JSON expression that will always evaluate to true, ex. :

{
  "%%user.id": "%%user.id"
}

In the write document permission we set the rule to use our function to decide, whether a document should be inserted. Learn more about Rule Expressions.

{
  "%%true": {
    "%function": {
      "name": "isInsertionAllowed",
      "arguments": [
        "%%user.id"
      ]
    }
  },
  "%%user.id": "%%this.userId"
}

The Write advanced filter will call our previously created function. The function will return whether the user's insertion request will be accepted. The second condition makes it unable for the user to provide a different userId that their actual. If a user attempts to insert a document with userId "a", it will be rejected.

After you are done with that, deploy your changes.

Go to App Users on the left side panel and add two users with any email and password. The email doesn't matter since we won't be verifying it anyway.

Testing configuration

For creating a web app, you would need a web SDK. The SDK is hosted on a CDN under the following address: https://unpkg.com/realm-web/dist/bundle.iife.js.

We won't be writing the web app though, we will use adder.html. The only important thing in the adder.html is the following part (you should change the app id from appliaction to the one, that you get when pressing the copy button, in the upper left corner near the name of your Realm app and the home icon):

const app = new Realm.App({ id: "application" });

async function loginEmailPassword(email, password) {
    const credentials = Realm.Credentials.emailPassword(email, password);
    const user = await app.logIn(credentials);
    console.assert(user.id === app.currentUser.id);
    return user;
}

This code logs into Realm SDK application with user credentials and then you are allowed to perform standard operations. Of course our rules should disallow a single user to post two consecutive sentences in a row. Use adder.html to test if your configuration is working properly with two different users you created.


Project - part 2

Task: Write a Function

Now we have to set up a function that returns count of sentences. It will return the number as a string in a JSON, like: { number: ... }. Use the same function settings and name it sentenceCount.

Hint: use testing console below to run the function and check its output, you can also perform console.log.

Code Solution
exports = async function(arg){
  const mongodb = context.services.get("mongodb-atlas");
  const db = mongodb.db("fusion");
  const coll = db.collection("sentence");
  
  return { number: String(await coll.count()) };
};

HTTPS Endpoint

In the beginning you learned that these functions can be executed on various triggers. Rules aren't the only possibility. Let's set up a HTTPS endpoint.

endpoints list

Our endpoint will be for GET requests and it will respond with JSON result. Here you should copy the second URL under the Operation Type as later we will use it to test the endpoint.

endpoint configuration 1

In the Function option, select the function that you created earlier in the task. As you can see endpoints can be also used for user creation.

endpoint configuration 2

After deployment, use the copied curl command to check if your endpoint returns a JSON with appropriate sentence count.


Project - part 3

Validation

There is one more configuration left - document validation. We will use MongoDB Compass for that, you can download it here.

Open Database Access on the left side panel. EDIT you user. Under Built-in Role select Atlas Admin. It is required to create validation rule through Compass. If you forgot your user's password, you can also change it here. Click Update User.

atlas admin user role

Click Data Services and then click Connect on your cluster. Under Access your data through tools select Compass. Copy the connection string from the second point, replacing < password > with your password.

connect with Compass

Open MongoDB Compass, connect with copied and modified connection string, and go to fusion database, sentence collection and then to Validation tab.

validation view

Set the following rule, with Validation Action set to Error and Validation Level to strict:

{
   "$jsonSchema":{
      "bsonType":"object",
      "required":[
         "_id",
         "userId",
         "content"
      ],
      "properties":{
         "_id":{
            "bsonType":"objectId"
         },
         "userId":{
            "bsonType":"string"
         },
         "content":{
            "bsonType":"string",
            "minLength":10,
            "maxLength":100
         }
      },
      "additionalProperties":false
   }
}

validation rule setup

Now users will be unable to insert documents with redundant fields and sentence lengths will be limited. When they try to insert invalid document, they will encounter an error preventing them.


End

In this comprehensive tutorial, you examined the serverless function concept and explored MongoDB Realm. You successfully configured user authentication, serverless functions, HTTPS endpoints, collection roles, and validation rules. Now, you have a solid understanding of the impressive capabilities offered by MongoDB Atlas and how to leverage them effectively. To further enhance your skills, it is highly recommended that you experiment with Realm and consider adding more functionality to adder.html. Wishing you good luck and an enjoyable MongoDB journey!

Lucas Hazardous

About

Extensive MongoDB Realm tutorial to explore serverless functions.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Languages