Title: Should You Do Web Scraping in the Back End? Let’s Discuss
Hey folks! So, I’ve been tinkering with this idea of doing web scraping in the back end for a project. But I’m kinda torn—should you do web scraping in the back end, or is it better to handle it elsewhere?
Pros:
- Keeps things clean on the front end.
- Easier to schedule/scrape at scale.
- Less likely to get blocked if you rotate IPs properly.
Cons:
- Can slow down your server if not optimized.
- Legal/ethical gray areas (depends on the site).
- Maintenance headache if sites change their structure.
What’s your take? Anyone here done it before? Any gotchas I should watch out for?
Also, if you’ve got tips on best practices (rate limiting, caching, etc.), drop ’em below!
Cheers! 🍻
Hey folks! So, I’ve been tinkering with this idea of doing web scraping in the back end for a project. But I’m kinda torn—should you do web scraping in the back end, or is it better to handle it elsewhere?
Pros:
- Keeps things clean on the front end.
- Easier to schedule/scrape at scale.
- Less likely to get blocked if you rotate IPs properly.
Cons:
- Can slow down your server if not optimized.
- Legal/ethical gray areas (depends on the site).
- Maintenance headache if sites change their structure.
What’s your take? Anyone here done it before? Any gotchas I should watch out for?
Also, if you’ve got tips on best practices (rate limiting, caching, etc.), drop ’em below!
Cheers! 🍻
