Introduction to POJOs
POJO is a term coined by Martin Fowler, Rebecca Parsons, and Josh Mackenzie in September 2000. It is an ordinary Java object, but what makes it plain old is not what it should do but rather what it should not do.
A Java object can be a POJO in the following circumstances:
- The Java object does not extend from any class.
- The Java object does not implement any interfaces.
- The Java object does not use any annotations from outside.
What these three restrictions lead to is a Java object that is not dependent on any other library or object outside of itself and is self-contained d enough to perform its logic on its own. You can easily embed POJOs in any Java environment due to their portability, and because of Java’s platform independence, they can be run on any machine.
H2O can export trained models in the form of POJOs. These POJO models can then be deployed and used to make predictions on inbound data. The only dependency on using...