...
| Parser | Pros | Cons | |
|---|---|---|---|
| Jackson | Consistent conversion of numerics | Slower Read | |
| GSON | Faster Reads | Converts numerics to Doubles |
Resolution
It would make the most sense to use GSON as much as possible as it is the faster than Jackson. However the practicality of Jacksons parsing cannot be overlooked. Therefore it would make sense to use the Jackson parser in this scenario. We also don't want to have or create a Jackson mapper and GSON mapper object in the same file however as the memory cost is quite high.
...
...
Consensus
Current Team Consensus is to use the Jackson Parser mainly due to the benefit of being able to parse numerical objects to the correct type and because the magnitude difference between the two parsers is in microseconds.
CPS-NCMP
- CpsDataPersistenceServiceImpl.java is using two mapper objects, GSON and Jackson, should be just Jackson
- NetworkCmProxyInventoryController.java is using the Jackson mapper where the GSON could be used instead
- NetworkCmProxyDataServiceImpl.java is using the Jackson mapper where the GSON could be used instead
...