Subdomains and subdirectories are very different things. A subdomain (blog.a2k.com) doesn't need to be on the same server as the root domain (a2k.com). Whereas a subdirectory does. This means that if you're serving something different from a subdomain, it's a lot easier to set up. BUT, subdomains count as separate domains for SEO. So blog.a2k.com is as useful for a2k.com ranking as random2k.com would be.
Thanks didn't knew that. Follow up question. Won't my server get loaded with all my HN traffic on the static page because in turn it runs on an Express Server ?
I setup Express Server & have 2 routes /static & /dynamic & my /static route just serves static pages but it would still crash my server down if many people visit on my site (/static route), right ?
What I want is if many people are on my /blog page it shouldn't affect my server because all my pages are static & it should only get affected if lot of people are on my /apps page.
Your server IS affected. But static routes can be cached, and traffic to a server cache can be freaking huge before it affects you. Also, you can get cloud flare or some other external service to handle that cache, and they can handle Super Bowl amounts of traffic.
Even with HN traffic, you'll be lucky to get shot down. I've run my product (www.blankpage.io) on the smallest Heroku dynamo running Expressjs and I've never been shot down. Despite being first on product hunt etc.
I'll try to make it first. I'm overthinking a lot. If it crashes, then I might change the process or I'll ping you then for advice. For now, I'll be making my /blog route a static page running Gatsby & /apps will contain all my apps. The problem is I don't want to buy 100 domains if I make that many one-of apps. So I'm making one /apps route which will incorporate all my apps each serving a different dynamic page. Lets see how this goes.
Subdomains and subdirectories are very different things. A subdomain (blog.a2k.com) doesn't need to be on the same server as the root domain (a2k.com). Whereas a subdirectory does. This means that if you're serving something different from a subdomain, it's a lot easier to set up. BUT, subdomains count as separate domains for SEO. So blog.a2k.com is as useful for a2k.com ranking as random2k.com would be.
Thanks didn't knew that. Follow up question. Won't my server get loaded with all my HN traffic on the static page because in turn it runs on an Express Server ?
I setup Express Server & have 2 routes
/static&/dynamic& my/staticroute just serves static pages but it would still crash my server down if many people visit on my site (/staticroute), right ?What I want is if many people are on my
/blogpage it shouldn't affect my server because all my pages are static & it should only get affected if lot of people are on my/appspage.Your server IS affected. But static routes can be cached, and traffic to a server cache can be freaking huge before it affects you. Also, you can get cloud flare or some other external service to handle that cache, and they can handle Super Bowl amounts of traffic.
Even with HN traffic, you'll be lucky to get shot down. I've run my product (www.blankpage.io) on the smallest Heroku dynamo running Expressjs and I've never been shot down. Despite being first on product hunt etc.
I'll try to make it first. I'm overthinking a lot. If it crashes, then I might change the process or I'll ping you then for advice. For now, I'll be making my
/blogroute a static page running Gatsby &/appswill contain all my apps. The problem is I don't want to buy 100 domains if I make that many one-of apps. So I'm making one/appsroute which will incorporate all my apps each serving a different dynamic page. Lets see how this goes.