Portfolio ↗

Offline-First

Treating connectivity as an optimisation, with a local store as the source of truth.

5Questions
10Flashcards
2Terms
Drill this topic All of Edge, Mobile & IoT
Questions

5 to work through

  1. advanced

    A courier application must work where connectivity is intermittent. What must be designed rather than assumed?

    2 min answer
  2. advanced

    A field application must work fully offline for hours and sync when connectivity returns. How should conflicts, permission changes and schema migrations on the device be handled?

    3 min answer
  3. advanced

    A field service app must work offline. Engineers book parts from a shared inventory. What is the design problem?

    2 min answer
  4. advanced

    Delivery couriers work in areas with intermittent connectivity and must complete jobs regardless. What does offline-first require beyond local caching?

    2 min answer
  5. advanced

    You are designing a field-service application for engineers who work in basements and rural sites with no reliable connectivity. What is the architecture, and what are the decisions that will bite later?

    3 min answer
Terminology

2 terms in this topic

pattern

Local First Write

Committing to local storage first and treating the server as an eventual replica, which makes the interface responsive and connectivity an optimisation.

 pattern

Offline-First Architecture

Treating the local device store as the primary source the application reads and writes, with the network as an asynchronous replication channel.
Edge, Mobile & IoT

Neighbouring topics

Edge, Mobile & IoT

General material on architecture beyond the data centre boundary.

3 quiz 6 cards 2 terms

Mobile App Architecture

Layering, navigation, background execution, and the platform rules you do not set.

5 quiz 8 cards 4 terms

Sync & Conflict Resolution

Two devices that both changed the same record while neither could see the other.

4 quiz 7 cards 4 terms

CRDTs

Data types that converge without coordination, and the semantics you must accept.

5 quiz 9 cards 3 terms

Mobile Release Strategy

Store review, staged rollout, and supporting versions you can never force off.

5 quiz 11 cards 3 terms

Push & Background Work

Delivery that is best-effort, and an operating system that will kill your process.

4 quiz 10 cards 3 terms

Device Identity

Identifying a thing rather than a person, and rotating a credential you cannot type.

5 quiz 10 cards 2 terms

Edge Compute Topologies

Regional, metro, on-premises and on-device, and what each tier is genuinely for.

4 quiz 9 cards 2 terms

Edge Functions

Short-lived compute at the CDN, its runtime limits, and what must stay at origin.

4 quiz 11 cards 3 terms

Edge Data Consistency

Replicated read state at hundreds of locations, and writes that still go to one.

4 quiz 10 cards 3 terms

IoT Ingest Architecture

Millions of small, unreliable, frequently duplicated messages arriving continuously.

5 quiz 11 cards 2 terms

Device Provisioning

Getting identity and configuration onto hardware at manufacture or first boot.

4 quiz 9 cards 3 terms

Fleet Management

Inventory, health, configuration and grouping across devices you will never see.

5 quiz 8 cards 5 terms

OTA Updates

Updating firmware over a flaky link, with rollback, and without bricking the device.

5 quiz 10 cards 6 terms

Constrained Protocols

MQTT, CoAP and their kin, chosen for power, packet size and intermittent links.

5 quiz 10 cards 4 terms

Device Telemetry at Scale

Deciding what a device sends, how often, and what is aggregated before it leaves.

4 quiz 8 cards 5 terms

Digital Twin

A server-side model of a physical thing's reported and desired state.

4 quiz 8 cards 3 terms

Edge Security & Attestation

Secure boot, hardware roots of trust, and proving what is running on a device.

4 quiz 9 cards 4 terms

Physical-World Failure Modes

Power loss, tampering, clock drift, thermal limits, and a truck through the fibre.

4 quiz 9 cards 5 terms