Repository navigation
Hosting #114
Description
I think it's about time we talk about what we want to do after the course is over. Do we want to keep hosting on my WebFaction account (which is basically free)? Do we want to go with something more elastic in case we get a sudden surge of traffic? Do we want to split the difference and use some kind of CDN to serve the front-end but keep the back-end on a central server?
On my hardware, the back-end can respond to about 200 requests per second (not counting loading the front-end). The front-end is big, though.
Activity
cdelahousse commentedon Apr 5, 2013
I think this is a question we should answers a bit further down the road. We don't have much in terms of users nor functionality. Once our app becomes a bit more polished, we should revisit this question.
For now, I think WebFaction is fine.
bheesham commentedon Apr 5, 2013
Well, I have a webfaction too. I can look into a way for my redis, to talk to your redis and we'll have a backup. It might be possible to do some reverse proxying.
spratt commentedon Apr 5, 2013
It would be wicked if we could do some sort of CDN type thing. Since your server is in Europe and mine is in the US, if we each served to requests coming from nearby it would be faster for folks.
psimonyi commentedon Apr 6, 2013
Recently read: http://www.peterbe.com/plog/never-put-external-javascript-in-the-head
Summary: minimize DNS lookups.
spratt commentedon Apr 7, 2013
If the whole front-end is loaded by CDN, the extra DNS lookup would only happen when querying the back-end.
spratt commentedon Apr 7, 2013
Actually, we're already guilty of doing this to get the persona library.
psimonyi commentedon Apr 8, 2013
I thought the Persona library was loaded asynchronously. (But we should not show the button until it's loaded... separate issue, I guess.)
spratt commentedon Apr 8, 2013
Persona is loaded by require...which I think is async.