Like most modern applications, Martini is flexible enough to accommodate different deployment architectures. Depending on how you plan to use it, one setup may be preferable over the other. Certain scenarios call for different set-ups and in this page, we shall briefly discuss the most common of them.
After deciding which servers would host Martini, perhaps the next step is to determine the architectural design of your server(s).
In this case, it is important to know the deployment model of choice because some deployment models offer more flexibility than others. To summarize, an on-premise deployment would give you the freedom to set-up your instances however you want while deployments on TORO Cloud automatically assume and maintain a three-tier network architecture (high availability).
Below are typical configuration scenarios for Martini:
|Simple||A single Martini instance on a single machine (typically a desktop computer) for testing and inspection purposes.|
|Three-tier network architecture (simple)||The minimal configuration required for a three-tier network architecture.|
|Three-tier network architecture (high availability)||An extensive implementation of the three-tier architecture, ensuring availability with the use of back-ups and clustering.|
|Development||A staging environment used to replicate production environments.|
|Production||For live or public servers.|
|Clustered||Similar to the concept of the three-tier, high availability design; differing in how clusters are implemented.|
|Headless||For environments which forego the use of user interfaces.|
The following pages will describe each of these scenarios in more detail. If the need arises. you may use these as a basis for your own custom set-up.