JSON mapping is typically an application-level concern (JSON-P, JSON-B) because all transformations and bindings are reflected on application or client-level. Having support directly in the driver comes with several drawbacks as drivers need to either commit to a single library or provide support for multiple implementations (Jackso, GSON, Apache Johnzon). This isn't typically the thing you want to deal with.
Also, most JSON libraries work with blocking streams (InputStream, OutputStream) that is not Reactive-friendly.
Another approach would be to provide an extensible codec registry and optional codecs that users can register.
JSON mapping is typically an application-level concern (JSON-P, JSON-B) because all transformations and bindings are reflected on application or client-level. Having support directly in the driver comes with several drawbacks as drivers need to either commit to a single library or provide support for multiple implementations (Jackso, GSON, Apache Johnzon). This isn't typically the thing you want to deal with. Also, most JSON libraries work with blocking streams (
InputStream
,OutputStream
) that is not Reactive-friendly.Another approach would be to provide an extensible codec registry and optional codecs that users can register.