Monolith > Scrapper + Frontend

I really love this project, but there is one thing that makes me sad - data updates only ~once~ twice* every 1 day.
Why not move the scrapper to a separate service and make it run often?
It seems that splitting the project into two modules wont take much time, build doesnt deps on main project - isnt?

Start by mapping the scraper, frontend, and current build dependency described in the issue. Determine how the scraper can run as a separate service and what deployment or scheduling changes are required. Done means the scraper and frontend are independently separated and data updates can run more often.

Written by the indexing model from the issue text.