Member Avatar for alex.tepes

Hi, I need to host a Website I can develop but I want first some hosting solution opinions other from what I can get from my hosting provider company :)

The site will be built using php+mysql basically - i need *nix system.

It's about a big corporate website that will get at least 30-40 TB traffic per month from around 4 mil visits. Also it will have a big list of newletter subscribers so a lot of email will be sent.

So what solution you can recommend?

PS: I am not interested in pricing for now... I just want technical advice.

  • 3 Contributors
  • 2 Replies
  • 212 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by jamesl22

Dani AI

Generated

Short answer for : do not host this from home. Thirty to forty terabytes per month equals a sustained load on the order of 90–125 Mbps (1 TB/mo ≈ 3.09 Mbps, so 30 TB ≈ 92.6 Mbps; 40 TB ≈ 123.5 Mbps), which is continuous capacity — not just burst. 1 TB/mo * 8e12 / (30*24*3600) is the rough conversion. Residential links usually lack the upstream, redundancy, and contractual terms to run a production site at that scale. (citizenmaths.com)

Recommended architecture (technical, not pricing): put a CDN in front and keep large assets off your origin. Use object storage for media (S3 or equivalent) and a global CDN (CloudFront, Cloudflare or similar) to serve static and cacheable content — that will cut origin egress and improve latency worldwide. Behind the CDN run an autoscaling pool of PHP app servers (Nginx + PHP-FPM or similar) behind a load balancer, with aggressive HTTP caching, Varnish or edge-cache rules, and Redis/Memcached for sessions and object cache. (cloudflare.com)

Database, email and ops notes: scale MySQL with a managed clustered/replicated setup (read replicas or a Galera/Aurora-style cluster depending on write profile), use query caching and a DB proxy/connection pooler to avoid connection storms, and move long tasks to queues. For newsletters use a high-volume ESP (Amazon SES, SendGrid, Mailgun) rather than your origin SMTP; ESPs handle reputation, deliverability, and IP warmup. Add monitoring, log aggregation, automated backups, multi-AZ for DBs, and a WAF/DDoS protection plan before launch. (aws.amazon.com)

Notes tied to earlier posts: ’s home-hosting idea is technically feasible for tiny projects but unsafe here; ’s comparison-shopping tip is fine for small sites, but at 30–40 TB you’ll need a CDN + either enterprise dedicated servers or cloud-managed, auto-scaling architecture as described above.

Recommended Answers

All 2 Replies

Member Avatar for cwarn23

With 30 to 40 TB of traffic you would probably be best to A - host with your own server at home with an isp that accepts unlimited traffic or B - you can risk yourself in one of those online scams with unlimited traffic. Personally I would go for option A.

Member Avatar for jamesl22

There is a good comaprison website for things like this it's: http://www.free-webhosts.com/

Edited by jamesl22 because: n/a
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.