jackson-module-scala VS jsoniter-scala

The other comment is asking the right questions. But also how is it failing? Do you have an error message? Is JsonUtil part of Jackson? Do you need to be using https://github.com/fasterxml/jackson-module-scala with an object mapper?

As a workaround you can turn on ignoring of unknown properties on the level of object mapper instance like here, but beware in case your system accepts an untrusted input because it turns on DoS vulnerability.

The simplest JSON parsing library is Jackson.

https://github.com/FasterXML/jackson-module-scala specifically

I've updated results of benchmarks of 12 JSON parsers for Scala: - AVSystem's scala-commons - Borer - Circe - DSL-JSON - Jackson - jsoniter-scala - Play-JSON, - play-json-jsoniter - Spray-JSON - uPickle - weePickle - zio-json

What an amazing step by step explanation!

More than 2 years ago I found that byte array view var handles are quite suitable to cook efficient SWAR routines with Java/Scala.

See a lot of other examples of SWAR usage, like parsing Base16/64 string, java.time.* and number values directly from byte arrays:

https://github.com/plokhotnyuk/jsoniter-scala/blob/master/js...

Afaik dsl-json came up with a lot of improvements and inspired a several other libraries like JsonIter and jsonIter-scala. Jsoniter-scala by u/plokhotnyuk is probably the most optimized JSON library on the JVM at this point, and seems to power most of the Scala ecosystem. Some implementations/optimizations eventually made their way back into Jackson and other libraries.

I was on your place more then 5 years ago, when cut the 1st release of jsoniter-scala.

I've just increased compiler performance in ~1.5x times by adding these JVM options for the code cache

We have our own open-source code-generator that produces Scala code from Smithy. The code module is entirely dependency-free, and the generated code is not biased towards any library, be that http or json. We do however have out-of-the-box integration with jsoniter and http4s.

You can use jsoniter-scala. It is easy to use like upickle.

BTW, jsoniter-scala uses it for faster parsing and serialization using SWAR techniques, like here.

Probably you should have both codecs (for Foo and for its T) are implicitly available in the scope, like it is done in the following test for jsoniter-scala:

BEWARE: uJson is vulnerable under DoS attacks

Please see sources (and GitHub history of development) of jsoniter-scala as an example in the domain of JSON parsing and serialization.