Check out what's in the latest release of Kabanero Learn More
Close the table of contents

Contents

Tags

Developing microservice apps with the Node.js Express application stack

duration 40 minutes

What you will learn

Application stacks enable the development and optimization of microservice applications. With application stacks, developers don’t need to manage the full software development stack or be experts on underlying container technologies or Kubernetes. Application stacks are customized for specific enterprises to incorporate their company standards and technology choices. Developers access these stacks by configuring their development environment to point to a stack configuration.

In this guide, you’ll learn how to configure your development environment, then create and run a simple cloud native microservice based on the Node.js Express application stack. Finally, you’ll update the microservice that you created and deploy it to Kubernetes or serverless. Deployment to serverless is optional depending on whether you want to Scale to Zero.

Applications in this guide are written based on the Express API specifications, built and run with Node.js, and deployed to Kubernetes through a modern DevOps toolchain that is triggered in Git.

Prerequisites

  • Docker must be installed. For local cluster development on Docker Desktop, you can enable Kubernetes from the menu by selecting Preferences -> Kubernetes -> Enable Kubernetes. Other options include Minishift or Minikube.
  • Appsody must be installed.

Getting started

You are going to create an application that is based on a public stack from the Kabanero project. After configuring your local development environment, you are going to initialize a new project that is based on the nodejs-express stack.

Configuring your development environment

To check the repositories that you can already access, run the following command:

appsody repo list

You see output similar to the following example:

NAME        URL
*incubator https://github.com/appsody/stacks/releases/latest/download/incubator-index.yaml

Next, run the following command to add the URL for the public Kabanero stack hub:

appsody repo add kabanero https://github.com/kabanero-io/kabanero-stack-hub/releases/download/0.9.0/kabanero-stack-hub-index.yaml

Check the repositories again by running appsody repo list to see that your repository was added. The output is similar to the following example:

NAME        URL
*incubator https://github.com/appsody/stacks/releases/latest/download/incubator-index.yaml
kabanero   https://github.com/kabanero-io/kabanero-stack-hub/releases/download/0.9.0/kabanero-stack-hub-index.yaml

In this example, the asterisk (*) shows that incubator is the default repository. Run the following command to set kabanero as the default repository:

appsody repo set-default kabanero

Check the available repositories again by running appsody repo list to see that the default is updated:

NAME        URL
incubator https://github.com/appsody/stacks/releases/latest/download/incubator-index.yaml
*kabanero https://github.com/kabanero-io/kabanero-stack-hub/releases/download/0.9.0/kabanero-stack-hub-index.yaml

Recommendation: To avoid initializing projects that are based on the Appsody application stacks, it’s best to remove incubator from the list. Run the following command to remove the incubator repository:

appsody repo remove incubator

Check the available repositories again by running appsody repo list to see that incubator is removed:

NAME     	URL
*kabanero https://github.com/kabanero-io/kabanero-stack-hub/releases/download/0.9.0/kabanero-stack-hub-index.yaml

Your development environment is now configured to use the Kabanero application stacks. Next, you need to initialize your project.

Note: If your organization has created a stack hub that contains customized application stacks, you must configure your development environment to access them. After you have completed this guide, you can step through this section again to update your configuration to point to the URL for your organization’s stack hub. This configuration process is also described in Developing microservice applications with the CLI.

Initializing your project

First, create a directory that will contain the project:

mkdir -p ~/projects/simple-nodejs-express
cd ~/projects/simple-nodejs-express

Run the following command to initialize your Node.js Express project:

appsody init nodejs-express

The output from the command is similar to the following example:

Downloading nodejs-express template project from https://github.com/kabanero-io/collections/releases/download/0.9.0/nodejs-express.v0.4.8.templates.simple.tar.gz
Download complete. Extracting files from /Users/myuser/appsody/simple-nodejs-express/nodejs-express.tar.gz
Setting up the development environment
Your Appsody project name has been set to simple-nodejs-express
Pulling docker image docker.io/kabanerobeta/nodejs-express:0.4
Running command: docker pull docker.io/kabanerobeta/nodejs-express:0.4
0.4: Pulling from kabanerobeta/nodejs-express
..
..
Status: Downloaded newer image for kabanerobeta/nodejs-express:0.4
docker.io/kabanerobeta/nodejs-express:0.4
Running command: docker run --rm --entrypoint /bin/bash docker.io/kabanerobeta/nodejs-express:0.4 -c "find /project -type f -name .appsody-init.sh"
Successfully added your project to /Users/myuser/.appsody/project.yaml
Your Appsody project ID has been set to 20200515090805.07014400
Successfully initialized Appsody project with the nodejs-express stack and the default template.

Note: Some lines (..) are removed for clarity

Your new project is created, built, and started inside a container.

Understanding the project layout

For context, the following image displays the structure of the project that you’re working on:

Project structure

This project contains the following artifacts:

  • app.js, a sample javascript app
  • package-lock.json, a project build file
  • package.json, a project build file
  • test.js, a simple test

Running the development environment

Run the following command to start the development environment:

appsody run

The CLI launches a local Docker image that contains the Node.js Express runtime environment that hosts the microservice. After some time, you see a message similar to the following example:

[Container] Running command:  npm start
[Container]
[Container] > nodejs-express@0.4.8 start /project
[Container] > node server.js
[Container]
[Container] [Tue May  15 12:58:44 2020] com.ibm.diagnostics.healthcenter.loader INFO: Node Application Metrics 5.1.1.202003121616 (Agent Core 4.0.5)
[Container] [Tue May  15 12:58:45 2020] com.ibm.diagnostics.healthcenter.mqtt INFO: Connecting to broker localhost:1883
[Container] App started on PORT 3000

This message indicates that the project is started. Browse to http://localhost:3000 and you can see the splash screen.

Browser showing Appsody splash screen

You are now ready to begin developing your application.

Creating and updating the application

You are now going to create a new route that listens on http://localhost:3000/example.

Create a new file called example.js in your project folder and populate it with the following code:

var express = require('express');
var router = express.Router();
/* GET users listing. */
router.get('/', function(req, res, next) {
 res.send('NEW ROUTE LISTENING');
});
module.exports = router;

Save the changes.

Edit the app.js file and update the contents to match the following code:

const app = require('express')()
var exampleRouter = require("./example")
app.get('/', (req, res) => {
 res.send("Hello from Appsody!");
});
app.use("/example", exampleRouter);
module.exports.app = app;

Save the changes.

The development environment watches for file changes and automatically updates your application. Point your browser to http://localhost:3000/example to see your new route, which displays NEW ROUTE LISTENING.

Testing the application

If you are building an application that is composed of microservices, you need to test within the context of the overall system. First, test your application and perform unit testing in isolation. To test the application as part of the system, deploy the system and then the new application.

You can choose how you want to deploy the system and application. If you have adequate CPU and memory to run MiniShift, the application, and the associated services, then you can deploy the application on a local Kubernetes that is running on your computer. Alternatively, you can enable Docker Desktop for Kubernetes, which is described in the Prerequisites section of the guide.

You can also deploy the system, application, and the associated services in a private namespace on a development cluster. From this private namespace, you can commit the microservices in Git repositories and deploy them through a DevOps pipeline, not directly to Kubernetes.

Testing locally on Kubernetes

After you finish writing your application code, the CLI makes it easy to deploy directly to a Kubernetes cluster for further local testing. The ability to deploy directly to a Kubernetes cluster is valuable when you want to test multiple microservices together or test with services that the application requires.

Ensure that your kubectl command is configured with cluster details and run the following command to deploy the application:

appsody deploy

This command builds a new Docker image that is optimized for production deployment and deploys the image to your local Kubernetes cluster. After some time you see a message similar to the following example:

Deployed project running at http://localhost:30262

Run the following command to check the status of the application pods:

kubectl get pods

In the following example output, you can see that a simple-nodejs-express pod is running:

NAME                                    READY   STATUS    RESTARTS   AGE
appsody-operator-6bbddbd455-nfhnm        1/1     Running   0          26d
simple-nodejs-express-775b655768-lqn6q   1/1     Running   0          3m10s

After the simple-nodejs-express pod starts, go to the URL that was returned when you ran the appsody deploy command, and you see the splash screen. To see the response from your application, point your browser to the <URL_STRING>/example URL, where <URL_STRING> is the URL that was returned. For example, http://localhost:30262 was returned in the previous example. Go to the http://localhost:30262/example URL to see the deployed application response.

Use the following command to stop the deployed application:

appsody deploy delete

After you run this command and the deployment is deleted, you see the following message:

Deployment deleted

Testing with serverless

You can choose to test an application that is deployed with serverless to take advantage of Scale to Zero. Not all applications can be written to effectively take advantage of Scale to Zero. The Kabanero operator-based installation configures serverless on the Kubernetes cluster. Because of the resources that are required to run serverless and its dependencies, testing locally can be difficult. Publish to Kubernetes by using pipelines that are described later in the guide. Your operations team can configure the pipelines so that serverless is enabled for deployment.

Publishing to Kubernetes by using pipelines

After you develop and test your application in your local environment, it’s time to publish it to your enterprise’s pipeline. From your enterprise’s pipeline, you can deploy the application to the appropriate Kubernetes cluster for staging or production. Complete this process in Git.

When Kabanero is installed, deploying applications to a Kubernetes cluster always occurs through the DevOps pipeline that is triggered in Git. Using DevOps pipelines to deploy applications ensures that developers can focus on application code, not on containers or Kubernetes infrastructure. From an enterprise perspective, this deployment process ensures that both the container image build and the deployment to Kubernetes or serverless happen in a secure and consistent way that meets company standards.

To deliver your application to the pipeline, push the project to the pre-configured Git repository that has a configured webhook. This configured webhook triggers the enterprise build and deploy pipeline. For more information, see Working with pipelines.

Way to go! What's next?

What could make this guide better?

Raise an issue to share feedback

Edit or create new guides to help contribute

Need help?

Ask a question on Stack Overflow

Where to next?