Push & Background Work
Delivery that is best-effort, and an operating system that will kill your process.
4 to work through
-
intermediate
A courier app relies on a data-only push to trigger a background sync. The push provider's dashboard reports 99.3% delivered. Product reports that about 6% of couriers see stale job lists for hours, and support notices these users are disproportionately on low battery or older devices. Where do you look, in what order, and what is the misleading signal?
3 min answer -
intermediate
A mobile app syncs data in the background every 15 minutes. Users report data is frequently out of date. Explain.
2 min answer -
intermediate
A mobile application relies on push notifications and background processing for time-sensitive updates. What is unreliable, and what must the design assume?
1 min answer -
advanced
Design push and background work for a chat application delivering to hundreds of millions of devices.
2 min answer
3 terms in this topic
Background Work on Mobile
Work scheduled outside the foreground session, which mobile operating systems aggressively restrict to protect battery life.
conceptBest Effort Delivery
The guarantee push notification services actually offer — which is none — and the design consequences of building on a channel that may silently drop.
conceptPush Token Decay
The steady accumulation of push targets that no longer reach a device - which inflates fan-out cost and makes delivery metrics describe a list rather…
Neighbouring topics
Edge, Mobile & IoT
General material on architecture beyond the data centre boundary.
Mobile App Architecture
Layering, navigation, background execution, and the platform rules you do not set.
Offline-First
Treating connectivity as an optimisation, with a local store as the source of truth.
Sync & Conflict Resolution
Two devices that both changed the same record while neither could see the other.
CRDTs
Data types that converge without coordination, and the semantics you must accept.
Mobile Release Strategy
Store review, staged rollout, and supporting versions you can never force off.
Device Identity
Identifying a thing rather than a person, and rotating a credential you cannot type.
Edge Compute Topologies
Regional, metro, on-premises and on-device, and what each tier is genuinely for.
Edge Functions
Short-lived compute at the CDN, its runtime limits, and what must stay at origin.
Edge Data Consistency
Replicated read state at hundreds of locations, and writes that still go to one.
IoT Ingest Architecture
Millions of small, unreliable, frequently duplicated messages arriving continuously.
Device Provisioning
Getting identity and configuration onto hardware at manufacture or first boot.
Fleet Management
Inventory, health, configuration and grouping across devices you will never see.
OTA Updates
Updating firmware over a flaky link, with rollback, and without bricking the device.
Constrained Protocols
MQTT, CoAP and their kin, chosen for power, packet size and intermittent links.
Device Telemetry at Scale
Deciding what a device sends, how often, and what is aggregated before it leaves.
Digital Twin
A server-side model of a physical thing's reported and desired state.
Edge Security & Attestation
Secure boot, hardware roots of trust, and proving what is running on a device.
Physical-World Failure Modes
Power loss, tampering, clock drift, thermal limits, and a truck through the fibre.