Hi Prefect, I'm trying to build up my understandi...
# prefect-community
p
Hi Prefect, I'm trying to build up my understanding of how a flow gets registered and run, while what happens in the background. I tried to sketch a diagram (attached here). I'm curious, is there anything plainly wrong in this diagram? Is there another diagram of the Prefect Runtime Architecture that I can reference?
z
Hi @Peter Roelants -- there's a diagram on our roadmap but not one yet šŸ™‚ I'll take a look at yours quick.
This looks reasonably correct
ā€¢ Flow registration doesn't register it to run, it sends the flow metadata to the server ā€¢ You'd then trigger a run for a flow via the API/UI ā€¢ The FlowRunner will submit a TaskRunner to the executor that wraps execution of your task code, but that may be too detailed for your goals here
b
@Zanie Can a flow be triggered via some API call once its registered with the Prefect server?. While UI is fine, for automated workflow, API calls is a must.
z
Yep! The GraphQL API lets you do everything the UI does.
b
@Peter Roelants Are you putting this diagram on the github somewhere. Would interested to bookmark it for reference. TY
p
Thanks for the verification!
@BK Lau I quickly made it in lucid chart for my own understanding. However I could export it if you want? What format would you like it in? And where could I upload it?
b
.pdf or .png should be fine.
I certainly agreed that there should be an architecture diagram. I think the Agent<--> Runner side was obscure. I'm certainly in the mechanics of things
p
@BK Lau Please find a pdf version here
b
@Peter Roelants Cool. TY. FYI there's a small Prefect architecture diagram on this site.
Copy code
<https://github.com/flavienbwk/prefect-docker-compose>
šŸ‘ 1