bjrnt / seonbi-service Goto Github PK

The user might provide options such as maximumMatches = 3 when searching. Although this option should affect the final result, it should not affect the results returned for caching. As such, there needs to be a way to separate the fetching + scraping steps from the transformation step.

When there's a cache miss:

core      1. Scrape
core      2. Parse
service  3. Cache set
core      4. Transform

When there's a cache hit:

service  1. Cache Get
core       2. Transform

Currently, the telegram bot does not use caching, and the API endpoint does not allow options, so this doesn't need to be handled immediately.