You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am new to Seldon Core but familiar with KFServing. I find that the documentation about the service orchestrator is hard to understand. I cannot get why we need such an orchestrator and how it works.
I think we can improve it. We could have a graph like it and illustrate the workflow of orchestrator and help readers understand the design purpose of it.
The text was updated successfully, but these errors were encountered:
Yeah, I notice that we are migrating to golang implementation. The graph I provided here is just used in my company to show the workflow of the orchestrator, not intend to be used by the doc directly.
BTW, there is a question about https://github.com/SeldonIO/mlgraph . I am wondering why we do not use the executor approach and propose mlgraph in Kubeflow community to implement the infer graph.
Personally, I think the executor is flexible and easy to maintain.
I am new to Seldon Core but familiar with KFServing. I find that the documentation about the service orchestrator is hard to understand. I cannot get why we need such an orchestrator and how it works.
I think we can improve it. We could have a graph like it and illustrate the workflow of orchestrator and help readers understand the design purpose of it.
The text was updated successfully, but these errors were encountered: