Gson VS RxAndroid

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.

Since you mentioned java, there is RxJava and RxAndroid. Google general recommendation now is to use kotlin coroutines if you're considering writing your app with that.

RxAndroid

Well, as mentioned in the RxAndroid's Readme, it's only Android extensions to RxJava. It makes it easy to subscribe or observe on the main thread or a specific looper. So just focusing on learning RxJava should be enough. You can find many resources for that, here is a compilation: http://reactivex.io/tutorials.html

Project: RxAndroid (Android specific bindings for RxJava) Copyright (c) 2015 The RxAndroid authors. License (Apache License Version 2.0) https://github.com/ReactiveX/RxAndroid/blob/master/LICENSE