Design discussion - explicit usage of Jackson about jolt HOT 2 CLOSED

The primary use case when creating Jolt was to take ElasticSearch results and transform them into our external JSON data API format. The Java ElasticSearch client gives us JSON data already fully hydrated into Maps / Lists, hence we operate on fully hydrated Java objects.

We have a Jackson dependency, but again I try to keep it at arms length. In "jolt-core" it is a test dependency, from the utility module "json-utils".

About halfway thru the development I heard about Jackson's native Node based interface, which sounds cool.

I think there could be a "port" of Jolt to operate on Jackson Node interfaces, in the same way that Jolt could be "ported" to JavaScript, Python, etc. Eg, the Domain Specific Language that is the Jolt Transform Spec, could be "implemented" in many languages. Imagine the Json transform spec implemented as a Node.js library, that would be cool.

Thank you for your interest in Jolt. I am curious what you are looking to use it for?

from jolt.

Makes sense. I'll consider creating a port then.

Answering your question: I use JOLT in a high throughput back-end service to ease integration with number of services that have similar interfaces.

from jolt.