Hi @Sihan_Wang !
Thanks for your response! Yes, I have read the Migration Guide.
As far as I could see in the code, “server.run(…)” will redeploy all deployments, even if they don’t change. This seems to be confirmed by @architkulkarni in this post. However, even if “server.run(…)” checks the changes, every time I want to update a single model, among hundreds of independent deployments, I would have to build and submit a big graph with hundreds of deployments. Suppose I have two concurrent requests to update two distinct models, I will probably have trouble with that.
If Ray Serve is used to serve a set of related deployments that change together, deploying with this “big graph” makes sense to me. But if each model may change independently and even more frequently, I would prefer an API to create, update and delete individual deployments (as in Ray 1.13).