Create a Scalable Naming System

1

Redis

This is the most basic way to use our application, but we're not tracking what we've already used, so we'll need to add some logic to make sure we don't get the same name twice. For this, we'll need a datastore that is as scalable as our application. In this case, we'll use Redis, a very popular and scalable database, and ioRedis, a Node.js wrapper for Redis.

#Key-Value Database #NoSQL Databases #Databases 183 social mentions

2

Google Cloud Functions

In this case, we're going to use the gcloud command line tool to deploy our application as a serverless function to Google Cloud Functions. To accomplish this, we'll need to wrap our application in an asynchronous function expression. Update the following code: Src/index.js.

#Cloud Computing #Cloud Hosting #Backend As A Service 41 social mentions

3

Google Cloud Platform

If you've ever created a project with Google Cloud or Docker you might have noticed every new project gets a unique, randomly-generated name. This is an effective way to avoid naming collisions, with the added benefit of being able to easily track your projects. Let's look at how to create a scalable naming system like these, and how to put it to use in a few different ways.

#Cloud Computing #Backend As A Service #Cloud Infrastructure 167 social mentions