liveBook · Manning

JSON

As explained in Grokking Software Architecture

A text-based data interchange format representing structured data with objects, arrays, strings, numbers, booleans, and null.

JSON can keep related information together in a document: a customer profile, for example, can include nested address and order details. An application can retrieve that bundle in one database operation instead of joining separate tables. section 8.2.2

A supply-chain message

In a supply-chain exercise, players pass order quantities on slips of paper, standing in for microservices sending JSON payloads via HTTP. The message carries information between services, while delays show that communication takes time. section 12.8.1

Figure 8.3 Showing how NoSQL Document databases store data. Instead of splitting a customer and their orders across separate tables linked by Foreign Keys, all related information is nested into a single, self-contained document. When the application asks for Alice's profile, the database returns her orders at the exact same time; no expensive "Joins" required!

See how customer details and orders can be nested into one self-contained document. section 8.2.2

How Grokking Software Architecture covers it

How deep it goes
Explains JSON's role in nested documents and service messages, but does not detail its syntax or parsing.
Examples
Illustrates a customer profile with nested details and order-quantity messages passed along a supply chain.
What you can do after
Understand how JSON can bundle related data for retrieval and carry order quantities between services.
How it connects
Links JSON with NoSQL document databases, aggregates, relational databases, HTTP, and microservices.

Also explained in

Compare how 42 books explain JSON →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.