NEW
Also known as: JavaScript Object Notation
A lightweight, text-based data interchange format for representing structured data as name–value pairs and arrays.
DESCRIPTION
JSON is a widely used serialization format for web APIs, configurations, logs, and document databases. Its simple syntax maps naturally to programming language types and JavaScript objects. Tooling support is ubiquitous across languages and platforms. While human-readable, it lacks comments and has limitations such as number precision issues and no date type. Validation and schema evolution are commonly addressed with JSON Schema. JSON underpins many modern data exchange protocols and event formats.
ALTERNATIVE DEFINITIONS
ECMA International
JSON is a text format for the serialization of structured data.
Formal standard definition emphasizing serialization of structured data.
JSON.org
JSON (JavaScript Object Notation) is a lightweight data-interchange format.
Highlights lightweight nature and interchange purpose.
MDN Web Docs
JavaScript Object Notation (JSON) is a standard text-based format for representing structured data based on JavaScript object syntax.
Explains relation to JavaScript object syntax for practitioners.
IETF
JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format.
IETF RFC formalizes JSON for interoperable interchange.
RELATED TERMS
CSV BSON Avro Protocol Buffers REST API NoSQL Data Schema JSON Schema
COMPETING TERMS
KNOWLEDGE AREAS
Programming Languages Data Integration & Interoperability Software Engineering Data Engineering
TARGET AUDIENCE
Software Developer Data Engineer AI Engineer MLOps Engineer Analytics Engineer
EXTERNAL SOURCES
- Wikipedia - JSON
- IETF - Authoritative JSON specification
- JSON Schema - Guide to JSON Schema validation
TOP QUESTIONS
How does JSON compare to XML?
JSON is lighter and maps naturally to programming types, while XML offers extensible markup with schemas and attributes. JSON dominates modern web APIs.
Category: Differences
What are JSON’s limitations?
No comments, limited number precision, no native date type, and verbose for large binary data. Use JSON Schema for validation.
Category: Risks
Where is JSON commonly used?
REST/HTTP APIs, configurations, event streaming, and document-oriented databases such as MongoDB or Couchbase.
Category: Example
How do you validate JSON?
Use JSON Schema to define structure and constraints, then validate with language-specific libraries in CI pipelines.
Category: Requirements
What’s a common mistake when handling JSON?
Assuming all numbers are safe as floating-point. Use precise types or libraries for money and large integers.
Category: Mistakes
Is JSON human-readable?
Yes, but it’s primarily machine-oriented. Pretty-printing improves readability; comments are not part of the standard.
Category: Opinion
What alternatives to JSON exist for efficiency?
Binary formats like Protocol Buffers, Avro, or MessagePack can be more compact and faster.
Category: Alternatives
How do you handle dates in JSON?
Use ISO 8601 strings or epoch timestamps with clear conventions and validation.
Category: Best Practices
Is JSON suitable for streaming?
Yes, with NDJSON (newline-delimited JSON) or JSON lines for incremental processing.
Category: Best Practices