On the one hand this makes it more similar to that of Kubernetes terminology.
This might get confusing, as it is not the same thing as a cup controller handles persistence to and from disk.
However, I think the terminology is appropriate when contextualized into something like an MVC pattern.
In this sense, the WASM binaries are the core implementations of the controller actions (get, list, put and delete).
The rest of cup provides Models in the form of resource definitions and schema.
The API automatic provides the View.
Renaming the term Runtimes to Controllers.
On the one hand this makes it more similar to that of Kubernetes terminology. This might get confusing, as it is not the same thing as a
cupcontroller handles persistence to and from disk.However, I think the terminology is appropriate when contextualized into something like an MVC pattern. In this sense, the WASM binaries are the core implementations of the controller actions (get, list, put and delete). The rest of
cupprovides Models in the form of resource definitions and schema. The API automatic provides the View.