APIs

[arjunmenon]

Hey Would be important also to know about APIs. If consuming, how to connect to them or if serving, how to deliver them? Any real world language would almost always have to deal with APIs. That itself contributes to the point "TOO many HTTP requests"

In Server, we can also talk about important performance enhancive techiniques like caching - page and db, load balancers, etc.

Would be also nice to know of ways to do it yourself, for eg, instead of saying pay to CDN which can get costly overtime, how can we do it on your own if starting with a small project, like having a different subdomains(cookie-free) to serve static content.

[thedaviddias]

Hi @arjunmenon, you are pointing out interesting subjects indeed. I didn't want to go to deep with the server side because it's still a "Front-End" Checklist and I just wanted to have enough elements that a normal Front-End could handle it. (but don't hesitate to add more content to the repo and we could review later).

Instead of paying for a CDN, I generally use Cloudflare (free version). That's the free CDN I know... (and I need to add the link in the checklist)

[github-actions[bot]]

This issue has been automatically marked as stale because it has been open 40 days with no activity. Remove stale label or comment or this will be closed in 10 days. Thank you for your contributions!

[github-actions[bot]]

This issue was closed because it has been stalled for 10 days with no activity. You can always contact the maintainers directly for more information.