A File Can Replace Your Tile Server: The Engineering Behind PMTiles
How PMTiles moves map delivery into an indexed archive, what HTTP range requests actually buy you, and where caching, updates, and analytical queries still need engineering.
6 posts found
How PMTiles moves map delivery into an indexed archive, what HTTP range requests actually buy you, and where caching, updates, and analytical queries still need engineering.
Why limiting workers does not necessarily limit memory, how backpressure must reach admission, and how to account for queues, batches, retries, and ordering under a slow sink.
Why deployment status is not a UI label, but a consistency problem across databases, queues, workers, locks, reconcilers, Kubernetes, and user trust.
Why a PaaS control plane is really a reconciliation loop: desired state, observed state, transactional outbox events, and billing that cannot afford to lie.
Every retry loop, job queue, state column, and idempotency key is a piece of a durable execution engine. What Temporal, Restate, and Inngest actually solve, what they cost, and when a plain queue is still right.
Clean code feels good, but every layer of abstraction hides a tiny tax on performance and clarity. Here's why it matters.