Question 1

How do I set up custom key encoding in jsonista?

Accepted Answer

Use the `:encode-key-fn` and `:decode-key-fn` options when creating an ObjectMapper with `j/object-mapper`. The README provides an example with a reverse-string function to transform keys during encoding and decoding.

Question 2

Should I use jsonista or Cheshire for my Clojure project?

Accepted Answer

Choose jsonista if performance is critical and you need explicit configuration; it's faster in benchmarks. Cheshire might be better for simpler use cases or if you prefer a more Clojure-idiomatic API without deep Jackson integration.

Question 3

Can jsonista handle streaming large JSON files efficiently?

Accepted Answer

Yes, jsonista provides a streaming API documented in `docs/streaming.md`, which allows processing large JSON data without loading it entirely into memory, ideal for performance-sensitive applications.

Question 4

How to add support for Joda-Time dates in jsonista?

Accepted Answer

Integrate Jackson's JodaModule by adding it to the `:modules` list when creating an ObjectMapper. The README example shows using `(JodaModule.)` to enable serialization and deserialization of Joda-Time classes.

Question 5

Is jsonista compatible with Ring and Compojure?

Accepted Answer

Yes, jsonista is designed for web development and works well with Ring and Compojure, especially when used with Muuntaja middleware for handling content negotiation and JSON encoding/decoding in web requests.

Question 6

What are the performance benchmarks for jsonista compared to data.json?

Accepted Answer

The README includes detailed JMH benchmarks showing jsonista has significantly higher throughput, with encoding speeds up to 3x faster and decoding up to 1.5x faster than data.json across various data sizes from 10b to 100k.

jsonista

What is jsonista?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions