Two apps on two servers, no load balancer

Two apps on two servers means two of everything: two groups, two balancers or two pools, two rehearsals. The two to three hours are mostly the balancers; the fit of 5 reflects that most of this work is on the customer’s side.

Prerequisite work
two LBs or CF LB with two pools
Time to set up
2–3 h
Adapter
Snapshot or webhook
Fit
5/10

Prerequisites, time and fit are the ADR-0028 row for this case. Hetscale's own setup is about 15 minutes in every case; the rest is work on your side.

Steps

  1. 01
    One group per app

    A group is one set of identical servers behind one load balancer. Two apps are two groups; Solo includes one, so this case starts at two groups (Solo with an extra group, or Pro).

  2. 02
    Two load balancers, or one Cloudflare balancer with two pools

    Either a Hetzner load balancer per app with TLS and DNS moved to it, or Cloudflare Load Balancing with a pool per app and the firewall restricted to Cloudflare IPs.

  3. 03
    Move state out of both

    Databases, sessions and uploads off the servers; a node’s disk does not survive its removal.

  4. 04
    Connect, rehearse each group, go Live

    The Observe trial reports per group. One Rehearsal per group, then Live with minimum 2 each.

FAQ for this case

Can the two apps share one load balancer?

One Hetzner load balancer serves one group. With Cloudflare, one load balancer can carry two pools, one per app, which is the cheaper option here.

See what Hetscale would have done with your real data — connect read-only, get your report in minutes.

Connect read-only