>>105569421
yeah sorry the screenshot is confusing, t5 encoder is running over network for this, the tokenizer is actually on localhost
there's a task broker and results broker that the client is connecting to, these can run anywhere, on localhost here
there's a service registry which keeps track of task types and allows the task broker to open a port for each task type
the service monitor doesnt really do much atm but heartbeats are sent
the database writer is saving stuff to postgres, this is connected to the same results broker that the client is using