Understand Deno's isolate model, Deno KV global database, Deno.serve(), permission flags, and native TypeScript support.
0 / 5 completed
1 / 5
What is the Deno Deploy isolate model?
V8 isolate model: isolates start in microseconds (versus milliseconds for containers) because they share the V8 heap and JIT-compiled code globally. Deno Deploy distributes your code to many edge PoPs, selecting the closest isolate for each request, minimising latency.
2 / 5
What is Deno KV?
Deno KV: provides atomic transactions, range queries, and real-time watches. Data is replicated globally with strong consistency via FoundationDB under the hood. On Deno Deploy, it is available without any setup; locally it uses SQLite as the backend for development.
3 / 5
What is the purpose of Deno.serve()?
Deno.serve: introduced in Deno 1.35 as the stable HTTP server API. Deno.serve({ port: 8000 }, (req) => new Response("Hi!")) uses the same Request/Response API as the browser Fetch spec, making handlers portable between server and edge environments.
4 / 5
What permission flag is needed to make outgoing HTTP requests in a Deno script?
--allow-net: Deno's security model requires explicit permission. deno run --allow-net=api.example.com script.ts permits connections only to that host. Without the flag, any fetch() call throws a permission error at runtime, containing supply-chain compromises.
5 / 5
How does Deno's native TypeScript support differ from Node.js?
Native TS: Deno ships with a TypeScript compiler integrated into the runtime. You can run deno run script.ts directly. Types are cached after first compilation. In Node.js you need ts-node, tsx, or a build step. This zero-config experience makes Deno very ergonomic for TypeScript developers.