Subdomain or path for dev/stage/uat environments

- 1 minutes read - 184 words

In my previous two companies, everytime I used the subdomain way without thinking much about this. Recently I wondered the rational behind this decisions. I had the clear answers two days ago. Today I have the time to put it into this writing.

Factors

subdomain(dev.example.com)

subdomain reasons

path (example.com/dev/)

path reasons

server side performance

9

  • dns records point to differnent IP.

  • easier to setup scalable solutions than anycast etc.

5

no way to point to different IP. CDN rules like cloudflare page rules?

private dns resolving

10

cloud

1

  • reverse proxy

  • traffic cost

client side performance

10

  • one tab only have limited connections to a specific domain.

  • multiple domains are good for parallel fetching

5

one tab only have limited connections to a specific domain.

routing simplicity

8

  • managable routing conf per subdomain.

  • difficult to reuse routing rules among domains

8

reverse proxy conf

dev/delivery productivity(speed/velociyt)

10

  • delegate management of subdomain to devs, frequent changes.

  • Usually a subdomain is for a component or sites which have its subdomains such as cdn, api, backoffice etc for diffent purposes

5

Ops usaully will be the bottleneck.
comments powered by Disqus