INFO90002 Chap.11 NoSQL, JSON and Semi-Structured Data

NoSQL, JSON and Semi-Structured Data

NoSQL, JSON and Semi-Structured Data turns document model, schema flexibility and consistency trade-off into executable reasoning. The chapter's practical target is to select a data model from access pattern, integrity and evolution needs, so every explanation should connect syntax to program state, control flow and observable output.

Treat document model as a precise program object, not a loose label.

Identify its value or responsibility before execution, then trace what can read it, change it or depend on it. This makes hidden state changes visible before they become debugging guesses.

Use schema flexibility to explain the program's next move. Work through one representative input by hand and name the branch, iteration or call that follows.

If the trace cannot be stated, the code may run by accident rather than by understood design.

Bring in consistency trade-off as the test of structure.

Compare normal, boundary and invalid inputs; state the expected behaviour first; then use the mismatch between expectation and result to localise the defect.

For the application — select a data model from access pattern, integrity and evolution needs — write the smallest complete example that exposes the rule.

Explain why it works, what would break it and how the program should signal or recover from that failure.

Before running a NoSQL, JSON and Semi-Structured Data example, make a trace table with the important state before and after each operation. Include the value associated with document model, the control decision governed by schema flexibility and the output or object affected by consistency trade-off.

The table turns an unexplained result into a sequence that can be tested one transition at a time.

Test three inputs: an ordinary case, a boundary case and an invalid case. State the expected result for each before execution, then compare it with what the program actually does.

A useful test of schema flexibility isolates one rule; a test that changes several conditions at once cannot tell you which condition caused the failure.

Practise explaining the solution without reading the code.

For INFO90002, name the data representation, the control flow, the responsibility of each function or class and the reason the chosen design supports select a data model from access pattern, integrity and evolution needs.

This rehearsal is especially important when a written test or interview asks why the program works rather than whether it produces one correct output.

A complete NoSQL, JSON and Semi-Structured Data response should make the task visible before the detail: identify what must be decided, define the relevant terms, connect the evidence to schema flexibility, and use consistency trade-off to test the result.

The final sentence should answer the question actually asked rather than merely repeat the topic.

The controlling limit is specific: Schema-on-read still has a schema and moves its enforcement boundary.

Keep that limit beside the worked example, because it separates a careful INFO90002 answer from one that sounds confident but claims more than the task or evidence supports.

For revision, retrieve document model, schema flexibility and consistency trade-off without notes, explain their relationship aloud, then complete a changed version of the application: select a data model from access pattern, integrity and evolution needs.

Record the first point at which your reasoning fails and repair that move before attempting another case.

What this chapter covers

• 01

  document model

• 02

  schema flexibility

• 03

  consistency trade-off

• 04

  Applying document model

• 05

  Limits of schema flexibility and consistency trade-off

Worked example: NoSQL, JSON and Semi-Structured Data

Key terms

DDL, DML and DCL (CREATE/DROP/ALTER vs SELECT/INSERT/UPDATE/DELETE vs GRANT/REVOKE)

DDL defines database structures with commands such as CREATE, ALTER and DROP; DML queries or changes data with SELECT, INSERT, UPDATE and DELETE; DCL manages privileges with GRANT and REVOKE. In this chapter, use the concept when you select a data model from access pattern, integrity and evolution needs.

referential integrity; logical vs physical data independence

Referential integrity requires each foreign key to match an existing referenced key or be null when allowed; logical and physical data independence protect users from changes to schemas or storage respectively. In this chapter, use the concept when you select a data model from access pattern, integrity and evolution needs.

conceptual, logical and physical design (the database development lifecycle)

Conceptual design models business entities and relationships independently of technology, logical design translates them into a data model and constraints, and physical design specifies storage, indexes and implementation details. In this chapter, use the concept when you select a data model from access pattern, integrity and evolution needs.

NoSQL, JSON and Semi-Structured Data FAQ

Exam move

Reconstruct the relationship among document model, schema flexibility and consistency trade-off; complete the chapter application without notes; then test the result against this limit: Schema-on-read still has a schema and moves its enforcement boundary.

Working through NoSQL, JSON and Semi-Structured Data in INFO90002? Sia is AskSia’s AI Information Technology tutor — ask any INFO90002 NoSQL, JSON and Semi-Structured Data question and get a clear, step-by-step explanation grounded in how INFO90002 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.