Why database choice affects architecture in Deno - Visual Breakdown

Concept Flow - Why database choice affects architecture

Choose Database Type

↓

Data Model & Schema

↓

Query Patterns & Performance

↓

Scaling & Availability

↓

Application Architecture Design

This flow shows how picking a database type influences data structure, queries, scaling, and overall app design.

Execution Sample

Deno

const dbType = "SQL";
let architecture;

if (dbType === "SQL") {
  architecture = "Relational Model with ACID";
} else {
  architecture = "Flexible Schema with BASE";
}

This code chooses architecture style based on database type.

Execution Table

Step	Variable	Condition	Action	Result
1	dbType	dbType === "SQL"	Check database type	True
2	architecture	N/A	Set architecture to relational	"Relational Model with ACID"
3	dbType	dbType === "SQL"	No else branch executed	N/A
4	architecture	N/A	Final architecture chosen	"Relational Model with ACID"

💡 dbType is 'SQL', so architecture is set to relational model and code ends.

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
dbType	"SQL"	"SQL"	"SQL"	"SQL"
architecture	undefined	undefined	"Relational Model with ACID"	"Relational Model with ACID"

Key Moments - 2 Insights

Why does choosing SQL vs NoSQL change the architecture?

Because SQL databases use fixed schemas and ACID transactions, the architecture must support structured data and strong consistency (see execution_table step 2). NoSQL allows flexible schemas and eventual consistency, changing design choices.

What happens if we pick NoSQL instead?

The else branch would run, setting architecture to 'Flexible Schema with BASE' (execution_table step 3), which means the app design supports flexible data and different consistency models.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'architecture' after step 2?

A "Relational Model with ACID"

B "Flexible Schema with BASE"

C undefined

D null

💡 Hint

Check the 'Result' column in row with Step 2 in execution_table.

At which step does the code decide the architecture based on dbType?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look for where 'architecture' variable is assigned in execution_table.

If dbType was 'NoSQL', what would be the architecture value after execution?

A "Relational Model with ACID"

B "Flexible Schema with BASE"

C undefined

D null

💡 Hint

Refer to the else branch action in the code and execution_table step 3.

Concept Snapshot

Database choice affects app design:
- SQL: fixed schema, ACID, structured data
- NoSQL: flexible schema, BASE, eventual consistency
- Influences data model, queries, scaling
- Architecture adapts to DB strengths and limits

Full Transcript

Choosing a database type impacts how an application is built. If you pick SQL, the app uses a relational model with strict data rules and strong consistency. If you pick NoSQL, the app supports flexible data and eventual consistency. This decision affects data structure, query methods, scaling options, and overall architecture. The example code shows how architecture is set based on the database type. Understanding this helps design apps that fit the database's strengths.

Practice

1. Why does the choice of database affect the architecture of a Deno application?

easy

A. Because Deno only supports one type of database

B. Because all databases use the same query language

C. Because different databases require different data models and query methods

D. Because database choice does not affect application design

Solution

1. Step 1: Understand database types

   SQL databases use structured tables, while NoSQL databases use flexible document or key-value models.

2. Step 2: Connect database type to app design

   The app must use different data models and queries depending on the database type chosen.

3. Final Answer:

   Because different databases require different data models and query methods -> Option C

4. Quick Check:

   Database type affects data model = D [OK]

Hint: Database type changes data structure and queries [OK]

Common Mistakes:

• Thinking all databases use the same query language
• Assuming database choice doesn't affect app design
• Believing Deno supports only one database type

2. Which of the following is the correct way to import a SQL client library in a Deno project?

easy

A. require('postgres');

B. import { Client } from "https://deno.land/x/postgres@v0.17.0/mod.ts";

C. import Client from 'postgres';

D. const Client = import('postgres');

Solution

1. Step 1: Recall Deno import syntax

   Deno uses ES module syntax with URL imports, not CommonJS require.

2. Step 2: Identify correct import statement

   import { Client } from "https://deno.land/x/postgres@v0.17.0/mod.ts"; uses correct ES module import with a URL and named import.

3. Final Answer:

   import { Client } from "https://deno.land/x/postgres@v0.17.0/mod.ts"; -> Option B

4. Quick Check:

   Deno uses ES module imports = A [OK]

Hint: Deno imports use URLs and ES module syntax [OK]

Common Mistakes:

• Using CommonJS require syntax
• Using bare module names without URLs
• Using default import when named import is required

3. Given this Deno code snippet using a NoSQL database client, what will be the output?

const db = new NoSQLClient();
await db.insert({ id: 1, name: "Alice" });
const user = await db.find({ id: 1 });
console.log(user.name);

medium

A. Alice

B. undefined

C. Error: insert method not found

D. null

Solution

1. Step 1: Understand NoSQL insert and find

   The insert method adds a document; find retrieves it by query.

2. Step 2: Trace code execution

   Insert adds user with id 1 and name Alice; find returns that user; console logs 'Alice'.

3. Final Answer:

   Alice -> Option A

4. Quick Check:

   Inserted user found and logged = Alice [OK]

Hint: Insert then find returns inserted data [OK]

Common Mistakes:

• Assuming find returns undefined if no await
• Confusing insert with update method
• Expecting error due to missing await

4. This Deno code tries to query a SQL database but throws an error. What is the likely cause?

const client = new Client();
await client.connect();
const result = await client.query('SELECT * FROM users WHERE id = $1', [1]);
console.log(result.rows[0].name);

medium

A. The console.log statement is incorrect

B. The query syntax is invalid for SQL

C. The query method does not support parameters

D. The Client constructor needs connection options

Solution

1. Step 1: Check Client initialization

   SQL clients in Deno require connection details (host, user, password) in constructor.

2. Step 2: Analyze error cause

   Without connection options, client.connect() fails, causing query error.

3. Final Answer:

   The Client constructor needs connection options -> Option D

4. Quick Check:

   Missing connection info causes error = A [OK]

Hint: SQL clients need connection info on creation [OK]

Common Mistakes:

• Assuming query syntax is wrong
• Thinking parameters are unsupported
• Blaming console.log for error

5. You want to build a Deno app that handles complex transactions and relationships between data. Which database choice best fits this need and why?

hard

A. SQL database, because it supports ACID transactions and relational data

B. In-memory database, because it is fastest for all data types

C. NoSQL database, because it handles flexible schemas well

D. Flat file storage, because it is simplest to implement

Solution

1. Step 1: Identify app requirements

   Complex transactions and relationships require strong data integrity and relations.

2. Step 2: Match database features

   SQL databases support ACID transactions and relational models, ideal for this need.

3. Final Answer:

   SQL database, because it supports ACID transactions and relational data -> Option A

4. Quick Check:

   Complex relations need SQL ACID support = C [OK]

Hint: Use SQL for complex transactions and relations [OK]

Common Mistakes:

• Choosing NoSQL for complex relational data
• Assuming in-memory is best for persistence
• Using flat files for transactional integrity