2 ms·
Nice re-skin. Suggestions vs. the 500's: · Show the rest of the page if the HN content isn't loadable. The server doesn't seem to have any problem delivering
by password4321 5y ago
Nice re-skin. Suggestions vs. the 500's:
· Show the rest of the page if the HN content isn't loadable.
The server doesn't seem to have any problem delivering the static assets, which are the majority of the work. Server-side rendering is awesome, but there's got to be a way to not lose the whole layout on server error?
· Load the HN content from somewhere else client-side rather than proxying through your server.
I don't have experience to share the ideal source, but I do know HN has an official API. Implementing caching may be enough to allow the server to handle it.
Congrats on your project getting so much traffic!
- assemblylang 5y agogood points, yes I definitely should have implemented some caching logic, the 500s are due to rate limiting on the HN side I think. Wasn't expecting this much traffic! good lessons for next time and something to consider for future projects