Skip to content

Overview

Development

Overview

IDEs

API Explorer

Flexible Deployment Models

TORO Integrate's deployment models

Introduction

In the enterprise world where one size does not fit all and change is ever constant, the demand for flexibility is immense. TORO understands this need, which is why it built TORO Integrate to be customizable – starting from deployment.

TORO offers two production-level subscriptions that either:

  • Gives you the privilege to run your instance on top of TORO Cloud - featuring convenience, availability, and direct technical support; or
  • Empowers you to freely deploy and manage instances on your own, of that which leads to a doorway of other, countless alternatives and possibilities.

Aren't there three types of subscriptions?

The Desktop Edition is similar to the Server Edition in that, deployment and maintenance is left to the hands of the subscriber. However, we will leave the Desktop Edition out of this discussion as this type of subscription is not intended for production-use.

Available Deployment Models

The type of subscription you have determines not only your TORO Integrate instance's feature-use limitations1 but also the deployment options available to you and your organization. A license for the Cloud Edition gives you access to TORO Cloud; whereas a license for the Server Edition gives you the ability to deploy your TORO Integrate instance on the server of your choice, be it the server of a different cloud provider or your own provisioned hardware. But with a hybrid deployment, you won't have to choose because you can get the best of both worlds.

To summarize, it is possible to deploy your TORO Integrate instance using any of the four deployment models below:

While deployments on TORO Cloud guarantee convenience and care in the hands of TORO's experts, self-managed deployments such as public cloud and on-premise deployments offer more options in terms of configuration and customization.

TORO Integrate also uses other services

Aside from the TORO Integrate application itself, you will need to host other services required by TORO Integrate. These include, but are not limited to database servers, Solr servers, and message brokers.

No commitments

With TORO Integrate, you don't have to commit to a single deployment model permanently; to shift from one deployment model to another is a matter of backing up your application data, setting up the new instance under the chosen deployment model, and then updating your TORO Integrate instance's configuration data, ensuring that they point to the right resources.

TORO Cloud Deployment

TORO Cloud is TORO's take on distributing TORO Integrate as a SaaS application. It is a pay-per-use service2 that lets clients rely on TORO for the hosting, monitoring, and patch management of their TORO Integrate instances, freeing them of said responsibilities and allowing them to focus on what truly matters – developing integrations.

TORO Cloud deployments are characterized by:

  • Lack of hardware investments
  • Easy and quick setups
  • Zero need for maintenance as updates are automatically applied, ensuring that you always have the latest version of TORO Integrate running
  • Improved dependability of machine to machine software and data storage
  • Scalability; flexible storage and computing capacity
  • Cost-effectiveness due to reduced operational costs3
  • The ability to manage data from anywhere

This type of deployment requires a license for TORO Cloud.

TORO Cloud deployment architecture

Instances on TORO Cloud implement a three tier, high availability network architecture.

Public Cloud Deployment

With a Server license, you can opt to deploy TORO Integrate using cloud computing services from AWS, Microsoft Azure, Google Cloud, Alibaba Cloud, or others of the like. This type of deployment is ideal for companies that already have existing servers or data repositories hosted by public cloud providers or those that require their data center to be in a specific geographic location.

Public cloud deployments are characterized by:

  • Lack of hardware investments
  • Self-managed software installation and configuration which means the subscriber has:
    • Internal oversight of the deployment
    • Can customize and fine tune the server configuration
    • Absolute control of the instance's application data

On-Premise Deployment

An on-premise deployment means TORO Integrate will be deployed using the company's own provisioned hardware and software. The company, which also owns the servers, has direct access to the local data repositories, thereby giving them more control over their own data.

On-premise deployments are characterized by:

  • Hardware investments which also means the subscriber is responsible for maintaining the provisioned hardware
  • Self-managed hardware setup and software installation and configuration which means the subscriber has:
    • internal oversight of the deployment
    • can customize and fine tune the server configuration
    • absolute control of the instance's application data
  • Offline availability

This type of deployment requires the Server Edition of TORO Integrate.

Hybrid Deployment

A hybrid deployment model is a deployment model that combines two or more of the deployment models above. This type of deployment model is recommended for instances where your organization may benefit from a combination of deployment models. For example, if you require your own server (public cloud or on-premise) but would like to have the TORO-managed option for your public facing instance, then a hybrid of a self-hosted solution (public cloud deployment or on-premise deployment) plus TORO Cloud would be the ideal solution.

With this type of deployment, data will have to be shared between instances. This means all instances will have to be configured so that they point to the same resources.

Deciding Factors

Choosing the right deployment model for your organization is not a measly task; your choice could either slow you down or put your business on top. Here are the factors you need to consider when choosing which deployment model to use for your TORO Integrate instance:

  • Responsibility of setup and maintenance

    Self-managed deployments will require a team of system administrators as the process of setup and deployment may involve4:

    • Setting up your server's hardware and software
    • Setting up the architecture of TORO Integrate and the family of services it requires
    • Dealing with your public cloud provider's technology, which can be very specific

    Meanwhile, TORO Cloud subscribers are freed from the responsibility of setup and maintenance as TORO will automatically set-up your instance for you using predefined configurations, and are backed up by TORO's team of experts.

  • Software and hardware configuration options

    With self-managed instances, you can pick out your server's operating system, use a load-balancer like NGINX, run your instance inside a container like Docker, set the firewall configurations of your server, and more! You will also have direct control over your application data.

  • Location

    The closer your server is to your group of target users, the faster it can respond; thus, it is ideal to position your server such that is located as close as possible to your users.


  1. Such as invoke limitations, supported SQL servers, etc. 

  2. or platform 

  3. Because you will not have to pay for hardware, or create a technical support team of your own; you also only pay what you use. 

  4. Depending on the type of self-managed deployment (public cloud deployment or on-premise deployment)