Traffic Distributor on MassiveGRID PaaS
Traffic Distributor is a smart load balancer that splits incoming HTTP and HTTPS traffic between two backend environments according to a percentage you set. It enables blue-green deployments, canary releases, A/B testing and instant failover between two versions of an application on MassiveGRID PaaS.
Both buttons open the MassiveGRID PaaS dashboard with Traffic Distributor pre-selected. The trial needs no credit card.
Traffic Distributor Package Facts
| Attribute | Value |
|---|---|
| Package | Traffic Distributor |
| Type | Application (installs a complete environment) |
| Category | DevOps & Admin Tools |
| Software vendor / project | Jelastic / Virtuozzo (package), NGINX |
| Licence | Open-source package (NGINX under BSD 2-Clause) |
| Runtime / stack | NGINX-based load balancer routing between two backend environments by weight |
| Regions | New York, London, Frankfurt, Singapore |
| Billing | Pay-per-use from $2.46/month ($0.003372/hour), no licence fee |
| Free trial | 14 days, no credit card |
| Uptime SLA | 100% |
What is Traffic Distributor?
Releasing a new version by replacing the old one in place is risky: if something is wrong, every user sees it. Traffic Distributor lets you run the new version alongside the old, send a small share of traffic to it, watch the metrics, and shift the balance to 100% when you are confident, or back to 0% in one click if you are not. The same mechanism supports A/B tests of two variants and manual failover between two environments.
The package deploys a highly available pair of NGINX nodes with a public IP and a simple configuration interface: two backend addresses and a weight. It also supports sticky sessions so a returning visitor keeps seeing the same variant. Backends can be any environment on the platform, or even external servers.
What the Traffic Distributor Package Deploys
Marketplace packages are not bare container images. One click provisions a complete, production-shaped environment on MassiveGRID infrastructure.
- NGINX load balancer nodes: Two NGINX containers for redundancy with a shared public IP, terminating SSL if required.
- Weighted routing configuration: Two backend targets with an adjustable traffic ratio, changeable at any time from the dashboard.
- Sticky sessions option: Cookie-based persistence so users stay on one backend for the duration of a test.
- Health checks and failover: Unhealthy backends are skipped automatically; set the ratio to 100/0 for manual failover.
Why Teams Choose Traffic Distributor
Blue-green and canary releases
Deploy the new version to a second environment, shift traffic gradually, roll back instantly.
A/B testing at the infrastructure level
Split real traffic between two variants without changing application code.
Zero-downtime migrations
Move users from an old stack to a new one, or between regions, by adjusting a percentage.
Backend-agnostic
Route to any PaaS environment or external endpoint; it works with the WordPress, Magento and Java packages alike.
How to Install Traffic Distributor on MassiveGRID PaaS
Installing the package takes three steps and a few minutes of waiting. No servers to provision, no configuration files to edit.
Open the installer
Click Install with free trial or Install to my account. The MassiveGRID PaaS dashboard opens with the Traffic Distributor package pre-selected, so nothing has to be copied or pasted.
Sign up or sign in
New to the platform? Sign up for the free 14-day trial, which needs no credit card. Existing customers sign in with their usual dashboard credentials.
Choose region and deploy
Name the environment, pick New York, London, Frankfurt or Singapore, and confirm. The platform builds every Traffic Distributor node, wires them together and hands you the live URL and credentials.
Who Runs Traffic Distributor on PaaS
Release engineering
Teams that want canary deployments without a service mesh or Kubernetes.
Marketing and product experiments
Testing two site versions with real users and comparing conversions.
Migration projects
Gradually shifting traffic from a legacy environment to a rebuilt one.
Why Run Traffic Distributor on MassiveGRID PaaS
Built for uptime. Traffic Distributor runs on MassiveGRID's high-availability platform, where every environment is covered by a 100% uptime SLA. Nodes live on redundant hosts, storage is replicated, and failed containers are restarted or migrated automatically.
Pay for what you use. Billing is hourly and per cloudlet (128 MiB RAM plus 400 MHz CPU). Vertical auto-scaling adds and removes cloudlets as load changes, so a quiet Traffic Distributor environment costs a few dollars a month and a busy one grows without a migration. Full details are on the PaaS page.
Your choice of jurisdiction. Deploy in New York, London, Frankfurt or Singapore and keep data inside the region your users or regulators require. MassiveGRID is ISO 9001 certified and GDPR compliant, and has run hosting infrastructure since 2003.
No lock-in. The package is a standard Jelastic Packaging Standard (JPS) manifest. You keep root-level access to the containers, can export the manifest, and can move the workload to any other Jelastic-compatible platform or to your own servers at any time.
Related on massivegrid.com: DevOps Support.
Traffic Distributor Questions
More from the Marketplace
Packages that are often deployed alongside Traffic Distributor, or that solve the same problem a different way. Browse all 84 packages.
Deploy Traffic Distributor Today
Start the free 14-day trial and have Traffic Distributor running in minutes. No credit card required.