With Jackson you will deal with POJO for network requests. The problem with POJO is that they are like plain C structs without encapsulation, so you inadvertently modify them.
At @Walmartlabs, my current employer we started adopting a wire model and a data model. The wire model is the POJO, it capture the raw data from services, and it is not visible to the application layer.
The wire model is used to create ( using a Builder pattern some times) the data model. The data model is immutable and may provide a more app layer friendlier interface .
In the world of data biding, the data model could be the one using on the biding
With Jackson you will deal with POJO for network requests. The problem with POJO is that they are like plain C structs without encapsulation, so you inadvertently modify them.
At @Walmartlabs, my current employer we started adopting a wire model and a data model. The wire model is the POJO, it capture the raw data from services, and it is not visible to the application layer.
The wire model is used to create ( using a Builder pattern some times) the data model. The data model is immutable and may provide a more app layer friendlier interface .
In the world of data biding, the data model could be the one using on the biding