Question 1

Is Jettison a drop-in replacement for encoding/json?

Accepted Answer

Yes, Jettison is designed to behave identically to encoding/json by default, with an extensive test suite ensuring compatibility, though it has minor differences like native time.Time handling and the omitnil tag option.

Question 2

How to configure Jettison for custom time formats?

Accepted Answer

Use the TimeLayout option with MarshalOpts to specify a layout compatible with time.AppendFormat. For example, set it to RFC3339 for ISO 8601 formatting, as shown in the advanced usage examples.

Question 3

Jettison vs jsoniter: which is faster?

Accepted Answer

Jettison generally outperforms jsoniter in benchmarks, especially for complex payloads and maps, with lower allocations. However, jsoniter might be easier for some use cases with its broader feature set including decoding.

Question 4

Does Jettison support JSON decoding?

Accepted Answer

No, Jettison is specifically a JSON encoder. For decoding, you must use encoding/json or another library, which can lead to inconsistency if you need both encoding and decoding in the same project.

Question 5

What are the main performance benefits of Jettison?

Accepted Answer

Jettison reduces marshaling time and allocations significantly, as benchmarks show up to 2x speed improvements over encoding/json for maps and complex types, with zero allocations in hot paths.

Question 6

Can Jettison handle nil pointers in structs?

Accepted Answer

Yes, Jettison supports the omitnil struct tag option to omit nil pointer fields, an improvement over encoding/json that gives more control over JSON output without custom marshaling.

jettison

What is jettison?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions