title: Shall I use POJO or JSONObject for REST calls
body: <p>Recently I have stumbled upon a situation where my new team is heavily using JsonObject for doing rest data interchange. Their view is while using pojo we are binding tightly with the rest service, while jsonObject gives freedom. Also it saves from unnecessary data serialisation at the same time reducing number of classes heavily.</p>
  
  <p>I have some points to encounter them as:</p>
  
  <ol>
  <li>Pojo gives more meaning to data and we are holding data with correct data type.</li>
  <li>If we need only 2 fields of 10 fields of json, we can deserialize to 2 fields class with <code>@JsonIgnore</code></li>
  </ol>
  
  <p>I don't know exactly on the cost of deserialisation, but somehow I have a feeling it shouldn't be much difference.</p>
  
  <p>Can someone help me understand which perspective is way to go ? </p>
  
  <p>Please provide some pros and cons of using POJO and JSONObject.</p>
  
  <p>Thanks</p>