Jackson VS Gson

To put things simply, this method findAllStreaming() takes an OutputStream to write the whole json response into. To write json into the stream chunk by chunk we are using JsonGenerator. JsonGenerator is provided by Jackson-Core. More detailed about how to write stream event is covered in this blog post by the author of the library.

Jackson already has some improvements for string-to-number conversion over stock JDK parser (https://github.com/FasterXML/jackson-core/pull/677). Would be great if they added faster number-to-string too.

🐞 Report issues here if you find any

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.

gson

The Gson library could parse the string response to a JSON.

This library works very well. https://github.com/google/gson

GSON

(but tbh I would definitely suggest looking into Gson)

However, I do know that there isn't an inbuilt JSON parser within Java. So, you will need to include a third-party JSON parser library within your project. I've had experience with using gson for doing this myself, and that library is also rather easy to use.