Ask HN: app.example.com vs. example.com/app for a browser based product?

Posted by Hammerhead12321 on Saturday January 25, 2025 @12:41PM
from the ask-hn dept.

I’m wondering if there are any particular pros or cons I may not be considering regarding deploying a browser based product on a subdomain versus a normal authenticated route.

( 2 comments | 3 points | on HN )

Re:Ask HN: app.example.com vs. example.com/app for a browser... by delogos on Saturday January 25, 2025 @01:01PM (#42823298)

Per RFCs, "example.com" (the bare domain name) must be a DNS A/AAAA record and cannot be a CNAME, which could limit your ability to use some anti-ddos/geo-loadbalancing solutions. Subdomain names (app.example.com) can be CNAME records.

[ Parent | on HN ]

Re:Ask HN: app.example.com vs. example.com/app for a browser... by meiraleal on Sunday January 26, 2025 @12:53PM (#42832068)

yes there are some peculiarities related to indexeddb, service worker and other web apis, app.example.com is another domain and might not share scope with example.com

[ Parent | on HN ]