DSL-JSON VS Gson

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.

You gotta at least add the top contender. I mean dsl-json is probably the fastest json lib java has to offer. I personally like Rob's avaje-jsonb, because I think the approach of no reflection, and doing everything via annotation processing is rad. (it also has some decent speed too)

Have you tried dsl-json instead of jsoniter? Should be faster.

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

Most of the time is spent in JSON parsing, specifically in AccessLogAggregator.parseLineJson. Within parsing, the majority of time is spent in org/json/JSONObject.. Since there are faster JSON libraries available, we'll switch to Gson and repeat the tests. To do this, we'll add the following method to our code:

In this concrete example we'll create 3 products. We can then convert this JSON to the list of products using Gson.

Gson has been in maintenance mode for at least 6 years. It's kind of a shame, because the API and implementation were a lot cleaner than Jackson.

For more information on native-image build arguments, please consult the GraalVM Native Image Options documentation. The next listing contains the contents of reflect.json, which contains a bunch of data classes that we need to serialize and deserialize with Gson, as well as our Lambda handler class which the runtime needs to instantiate based on the qualified class name passed to the Lambda function.

The loadModel() method is special. It needs to dynamically update the model path specified in the JSON-formatted template file according to the extraction path of the Jar package. Gson can be used to load and update the JSON object.

If you check out the Gson user's guide, there's a section titled "JSON Field Naming Support" which explains how to do this. There are also lots of examples if you google "gson rename field".

gson

I am not sure if this is what you are looking for, but allot of projects that I worked on used gson to convert between Java objects and JSON strings (https://github.com/google/gson). Maybe you should check it out.

Since this JSON contains the JSON representation of Java objects that are unknown in PoSh/.NET, all you could do is extract the provided object data (values), but not the objects themselves. In order to extract the "real" objects as they're defined, you'd have to start from the Java side, and use a tool like Gson.