High-level system architecture and dataflows #22
Description
Is your feature request related to a problem? Please describe.
An architecture-level blog post that explains the key components and dataflows that comprise RecipeRadar could be useful to help educate people - including potential contributors - about how the system works.
Describe the solution you'd like
A diagram could be fairly key for this. Something that indicates where recipe data is retrieved from (multiple websites - with squid on the outbound path to reduce load on those), the component that acceses them (the crawler, perhaps with an indication that it encapsulates recipe-scrapers), the lookup/parsing that occurs on the results, and how those are stored and indexed in the database and search engine -- before the api serves those to the frontend web application.
Boundaries in the diagram to indicate the client web browser context, server-side Kubernetes cluster, and external web content could be useful.
Describe alternatives you've considered
N/A
Additional context
N/A