CurrikiStudio Deployment Options

An Overview

What is CurrikiStudio’s Topology?

Components of the Curriki Infrastructure

A total of 7 containers comprise Curriki’s
current architecture:

 

  • Curriki API.
  • CurrikiStudio Client.
  • CurrikiStudio Admin Client.
  • Tsugi Framework.
  • Trax Learning Record Store (Optional).
  • PostgreSQL & MySQL databases.
  • Elasticsearch (Optional).

How Can I Deploy the Curriki Platform?

The Curriki infrastructure can be deployed using Docker.

Except for Elasticsearch, every component of the Curriki architecture is available as a Docker container.

 

  • The application containers are available on GitHub here.
  • The database containers are available on GitHub here.
  • An experimental container for deploying Elasticsearch is available here but we recommend installing using the instructions available here.

Where Can I Deploy the Curriki Infrastructure?

The Curriki infrastructure can be deployed to a variety of environments.

Cloud Providers

Deployment to the following have been tested:

 

  • AWS – Cloud Formation.
  • Oracle Cloud – Terraform Script.
  • Linode -Docker.
  • Azure – Docker.
  • Red Hat OpenShift – Kubernetes.

On Premise

Deployment to current stable Linux distributions (Centos, Ubuntu, Red Hat, Oracle Linux, etc.). Deployment to Windows is possible but not tested.

What is the Recommended Sizing for Curriki?

VM Shape: Minimum Recommendations

Application server

VM 1: 8GB RAM / 2 CPU

1 TB Block Storage

Database server

VM 2: 8GB RAM / 2 CPU

1 TB Block Storage

Elasticsearch server

VM 3: 8GB RAM / 2 CPU

1 TB Block Storage