ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
I'm designing the data layer for a small app on Deta Space, using Deta Base and Deta Drive, and I want to apply least-privilege access between components. My understanding from the documentation era is that data access is authenticated with long-lived, full-access keys that Deta treats as password-equivalent secrets, with no documented read-only or scoped va
I'm building a Deta Space app that runs a scheduled action (cron trigger declared in the Spacefile) to check a condition — for example, stale data or a quota threshold — and send a notification through a third-party channel like a Slack webhook or email. Since Space has no built-in alerting or notification subsystem, all of this logic lives in my own code. T
Concurrent Request Handling in Deta Base Deta Space employs a serverless architecture where the frontend is decoupled from the backend storage. Data persistence is managed through Deta Base, a NoSQL-like document store accessed via a REST-based API. When deploying Micro apps that require frequent state updates, the interaction between serverless functions an
Deployment Versioning vs. Data Persistence Deta Space separates the compute layer from the data layer via Deta Base. When an application is updated using the Deta CLI, the cloud environment routes traffic to the new build version. If a deployment introduces a critical failure, the standard recovery path involves redeploying a previous stable build version. S
Determine how Deta Base fetch pagination behavior without the 'last' cursor influences observed request latency and error patterns in deployed micros instances. Deta Space runs on managed Micros instances where the platform governs concurrent request handling, and the SDK abstracts underlying connection lifecycle, making it difficult to distinguish platform‑
Handling Duplicate Writes in Deta Base Deta Base provides a serverless NoSQL environment where data operations are performed via a REST API. While record-level updates are atomic, the standard API does not natively provide idempotency keys for complex write operations. When an application encounters a network timeout or a 5xx error during a write request, th
I'm designing a small app on Deta Space that uses Deta Base as its data store, and several request handlers can end up writing to the same key at roughly the same time (for example, incrementing a counter or updating a shared record). I want to understand what behavior I can rely on before choosing between a last-write-wins design and building my own coordin
The goal is to retrieve a subset of millions of documents from a Deta Base collection without triggering a full table scan, while still supporting cursor‑based pagination. Deta Base permits attribute‑based filters and a ‘limit’ parameter that defines the maximum number of documents returned in a single response. The official docs do not specify whether the l
detaspace