What Is JSON? A Foundational Guide to JavaScript Object Notation

Introduction

If you have worked on a modern web application, integrated an API, or edited a configuration file in the last decade, you have encountered JSON.

JSON, which stands for JavaScript Object Notation, is a lightweight, text-based data interchange format. It is incredibly easy for humans to read and write, and it is equally easy for machines to parse and generate.

In this foundational guide, we will explore the origins of JSON, break down its core syntax rules, compare it to its predecessor (XML), and look at the most common scenarios where developers utilize it today.

The History of JSON

Before JSON became the de facto standard, the web relied heavily on XML (eXtensible Markup Language) for asynchronous browser-to-server communication (the era of AJAX). However, XML was notoriously verbose and required complex, slow parsers.

In the early 2000s, Douglas Crockford popularized JSON as a simpler, more streamlined alternative. Because JSON's syntax was a subset of JavaScript, web browsers could parse it natively and effortlessly using the built-in eval() function (and later, the much safer JSON.parse()).

Over time, its simplicity won the developer community over. Today, it is recognized internationally under the ECMA-404 standard and is supported natively by almost every modern programming language.

JSON Syntax & Data Types

JSON data is written as name/value pairs (also called key/value pairs). It is built on two universal data structures:

• Objects: A collection of name/value pairs enclosed in curly braces {}.
• Arrays: An ordered list of values enclosed in square brackets [].

Supported Data Types

JSON supports exactly six data types:

• String: Text wrapped in double quotes. "name": "Alice"
• Number: Integers or floating-point numbers. "age": 28
• Boolean: true or false. "isActive": true
• Null: An empty or non-existent value. "middleName": null
• Object: Nested key/value pairs. "address": { "city": "Seattle" }
• Array: A list of values. "tags": ["developer", "designer"]

{
  "employee": {
    "id": 1042,
    "name": "John Doe",
    "department": "Engineering",
    "skills": ["JavaScript", "Python", "Go"],
    "isRemote": true,
    "manager": null
  }
}

JSON vs XML

While XML is still used in enterprise systems, SOAP APIs, and legacy applications, JSON has completely taken over the modern web. Here is why developers prefer JSON over XML:

Why Developers Use JSON

JSON is favored because it acts as a universal translator. A backend written in Python can query a database, serialize the data into a JSON string, and send it over the internet. A frontend written in JavaScript receives that string, parses it back into an object, and renders it to the user.

This decoupling means that the frontend and backend do not need to share the same programming language—they only need to agree on the JSON data structure.

Common Use Cases

• RESTful APIs: When you fetch data from modern services (like Stripe, Twitter, or GitHub), they return the data formatted as JSON.
• Configuration Files: Developer tools use JSON to store settings. Examples include package.json for Node.js, tsconfig.json for TypeScript, and VS Code settings.
• Data Storage: NoSQL databases like MongoDB store records as BSON (a binary representation of JSON), allowing for highly flexible, schema-less data storage.
• Web Tokens: JSON Web Tokens (JWTs) rely on base64-encoded JSON payloads to securely transmit authentication claims between parties.

Frequently Asked Questions