ユーザー

トラフィックが始まる場所。ドメインは1つのホストに解決されるので、ユーザーが取るリンクは1本だけです。

このページはまだ日本語に翻訳されていません。

Users stands for the people on the internet who type your domain into a browser or open your app.

When to place it#

  • You never place Users, and you cannot sell it. You act on its link instead.

  • Put DNS or a Load Balancer in front of your App Servers when the board refuses a second link from Users: one host is not enough.

How it works#

The Node sends every request kind in the current Era's mix (see Eras). Each request pays the user hop before it reaches your first Node. How many users you have depends on Apdex and growth, as Users and growth explains.

A domain resolves to one host, so Users take one routing link. To reach more than one App Server, link Users to DNS or a Load Balancer and let that Node split the traffic.

From the Series C Era, users live in four regions. Each region you open gets its own Users Node on its own tab. The GeoDNS Research sends each region's users to their own region, or to the nearest live one.

How it fails#

Users never fail by themselves, but everything they reach can.

  • If the one Node behind Users goes down, every request fails.

Certificate expired#

  • Signs: Every browser refuses the site, and a "Certificate expired" banner appears with a Renew button.

  • Do now: Press Renew on the banner. The certificate is issued again at once.

  • Prevent: Research Certificate automation.

BGP misconfiguration#

  • Signs: A routing change withdraws your Company from the internet, and users cannot reach any region. A banner appears with a Roll back button.

  • Do now: Press Roll back on the banner to undo the change.

  • Prevent: No Research prevents it, and it is rare.

Traffic spike#

  • Signs: Demand runs at ×3 to ×10 for minutes, and every card goes amber, then red.

  • Do now: Add copies or sizes to the Nodes that saturate. With Priority load shedding, set Shed low value on the App Servers.

  • Prevent: Keep spare capacity, add an Autoscaler or a CDN, and research Priority load shedding.

Bot surge#

  • Signs: The bot kind climbs on every card as scrapers arrive.

  • Do now: Place a WAF after Users. It stops bots at its block rate, and a higher paranoia level stops more of them.

  • Prevent: Research Web application firewall and place one.

DDoS#

  • Signs: Demand runs at ×50 of junk.

  • Do now: Select the WAF and press Under attack. It challenges every request. Without a WAF, nothing speeds it up; it ends on its own after at most 60 s.

  • Prevent: Research Web application firewall and Content delivery, and place both at the edge.

Tips#

  • Link Users to a Load Balancer, not to an App Server, as soon as you can afford one.

  • Put a CDN or WAF directly after Users: they work best at the edge.

ルール#

ユーザーは常にボード上にあります。設置も売却もできません。

一緒に使えるもの#

DNS、ロードバランサー、CDN、WAF、APIゲートウェイ