MangaDex infrastructure overview
mangadex.dev
MangaDex infrastructure overview
1–10 of 241 posts
Re: MangaDex infrastructure overview
#2>more than 10 million unique monthly visitors
>our ~$1500/month budget
I understand not wanting to show ads, but is there no way for the users to contribute to hosting costs?
Re: MangaDex infrastructure overview
#3It's a nice article, I guess, but the site is down (the one discussed in the article, not the blog post itself) for me.
Re: MangaDex infrastructure overview
#4>more than 10 million unique monthly visitors >our ~$1500/month budget I understand not wanting to show ads, but is there no way for the users to contribute to hosting costs?
A $5/mo premium plan would break even so quickly
Re: MangaDex infrastructure overview
#5It's a nice article, I guess, but the site is down (the one discussed in the article, not the blog post itself) for me.
It works fine for me: https://mangadex.org/
Re: MangaDex infrastructure overview
#6I'm amazed that their architecture doesn't include a CDN. These days I expect nearly all high traffic websites to make use of a CDN for all kinds of content, even content that's not cached.
They cited Cloudflare not being used due to privacy concerns. It'd be interesting to hear more about that, as well as why other CDNs weren't worth evaluating too.
Re: MangaDex infrastructure overview
#7I loaded the front page of Mangadex and it made 114 web requests including 10 first-party XHR requests, 30(!!!!) Javascript resource requests and somehow 4 font requests, without me interacting with the page. Clicking one of the titles on the front page resulted in nearly 40 additional requests.
Perhaps if you are limited by requests per second you could consider how many requests a single user is making per interaction, and if this is a reasonable number.
The website is impressively fast though, I'll give you that.
Re: MangaDex infrastructure overview
#8I'm amazed that their architecture doesn't include a CDN. These days I expect nearly all high traffic websites to make use of a CDN for all kinds of content, even content that's not cached. They cited Cloudflare not being used due to privacy concerns. It'd be interesting to hear more about that, as well as why other CDNs weren't worth evaluating too.
I think the usual argument re: Cloudflare on the privacy front is the fact that they pretty aggressively fingerprint users, and will downgrade or block traffic originating from VPNs or some countries. This is a natural side effect of those things often being tied to abusive traffic, and a lot of it is likely configurable (at least on their paid plans) but it often comes up around this.
Re: MangaDex infrastructure overview
#9I'm amazed that their architecture doesn't include a CDN. These days I expect nearly all high traffic websites to make use of a CDN for all kinds of content, even content that's not cached. They cited Cloudflare not being used due to privacy concerns. It'd be interesting to hear more about that, as well as why other CDNs weren't worth evaluating too.
It's effectively a warez site. There's a reason why they host in the places they do and can't be too picky about providers.
CF will also pass through things like DMCAs easily.
Based on their sidebar, it's probably hosted at Ecatel or whatever they are called now (cybercrime host) via Epik as a reseller, the provider famous for hosting far-right stuff.
Re: MangaDex infrastructure overview
#10[deleted]