Summary
We began this chapter by taking a high-level view of the transition from model building to model deployment. We saw that this transition is bridged for H2O by the MOJO, a deployable representation of the trained model that is easy to generate from model building and easy to deploy for fast model scoring.
We then took a closer look at the range of target systems MOJOs can be deployed on, and saw that these must run in a Java runtime but, otherwise, are quite diverse. MOJOs can be scored on real-time, batch, and streaming systems, usefully categorized as H2O Scorers (scoring software provided and supported by H2O), third-party integrations (software provided and supported by companies other than H2O), and your software integrations (software that you build and maintain).
This categorization of target systems helps us determine whether you can deploy the exported MOJO directly, or whether you need to wrap it in a Java class using the h2o-genmodel
API to embed it into the...