NATS is a high-performance messaging system for cloud native applications. In this guide we introduce it, and walk through how to use it in your first application.
Acorn has recently announced the launch of its cloud platform available for everyone at https://acorn.io. This platform offers users a sandbox environment where they can deploy Acorn applications for free. In this guide, we will outline the steps to deploy a simple application within this sandbox.
Visit https://acorn.io where you can log in just using your GitHub Account
Upon clicking the Login button, you’ll be directed to the authentication page.
After logging in, you’ll reach the Acorn dashboard, presenting you with several options:
This article will focus on deploying an existing Acorn.
We will demonstrate this using the VotingApp, a straightforward microservice application. We have used this application in a series of introductory articles on Acorn and in this self-paced Acorn workshop. To learn more about the VotingApp, you can review the code in Gitlab.
From the Acorn dashboard, start by selecting the Already have an Acorn option.
Next, choose From Acorn Image since we are deploying an already existing Acorn image from an OCI registry. Then, enter the image details:
Note: the path of this Acorn image docker.io/lucj/voting:v#.#.# specifies the image available in the Docker Hub OCI registry. The format v#.#.# enables Acorn to automatically update the application when a new tag appears in the registry.
After entering the information, click Deploy. The application will be created in the Pending state.
The status will shift to Provisioning, and additional details will be displayed, indicating the status of the application’s components.
Once all the application’s container are up and running, the status will change to Running.
Two contextual menus are accessible on the right:
The bottom icon leads to the application’s endpoints, the URL through which users can access web interfaces exposed to the outside:
Two HTTP endpoints are provided in this example:
Clicking these links opens the interfaces in new tabs.
The top icon toggles a menu offering several application management actions:
For example, to view the application logs, click View logs from this menu. A panel will appear at the bottom of the screen as shown below, displaying the logs of all the application’s containers.
A menu at the bottom allows you to select the container’s replica and to filter the logs.
Clicking the application name displays the main information:
Also, clicking the “plus” sign next to the application name expands the app and reveals details about its components:
Selecting a component opens a new panel providing detailed information such as:
The example below is an illustration for the result container:
More details are available for other components as well. The screenshot below shows the details of the volume backing the Postgres database, a 1GB AWS EBS. The volume backing the Redis database would show the same characteristics.
Similarly you can inspect the db-creds secrets which content was automatically generated when the application was deployed.
Once finished using the application, we can remove it using the Remove option in the application contextual menu.
In the previous part we explored some Acorn Cloud main features and saw the application deployment process through the UI. You can quickly deploy the application in your Acorn sandbox clicking the button below:
Note: you will be requested to authenticate first
As we saw in this tutorial, deploying an existing application in the Acorn sandbox is straightforward. All you need is a GitHub account, the application’s image and you’r good to go. An application running in the Sandbox will automatically shut down after 2 hours, For continuous operation and extra features, you might consider upgrading to the Acorn Pro plan.
You can also deploy applications directly using the Acorn CLI, which provides the same functionality from the command line.