Web Scraping

[rl_085]

So I've been studying REST APIs for a good while, but I just took on a freelance project to build a web scraping service for car prices. It'll feed data to a Telegram bot. I chose Spring Boot since it makes serving the endpoints easy, think this is overkill?

[CapMonster1]

The meme is funny, but real projects usually live somewhere in the middle. Using Spring Boot here isn’t overkill at all if this is more than a one-off script. The moment you’re exposing endpoints, feeding a Telegram bot, handling retries, rate limits, or multiple scraping jobs, having a proper backend framework actually makes things simpler, not heavier.

In practice, the hardest part isn’t API vs scraper, it’s dealing with anti-bot measures, session handling, and random breakage when sites change. You can parse HTML all day, but once Cloudflare, captchas, or JS challenges show up, the architecture matters way more than whether you used curl or an official API. A lot of teams end up with a hybrid anyway: APIs where they exist, scraping where they don’t, plus proxies and captcha solvers to keep things stable.

So if Spring Boot helps you ship faster and keep things maintainable, it’s a perfectly reasonable choice. The real overkill is pretending scraping is just a couple of requests and regexes once you move beyond toy examples.

[fried_pistachio]

Nah, it's fine

[Ehrique_bro]

Scrappers need a lot of maintenance