Deploy a Stateless Python Micro-App to Deta Space with Deta Base
Keep durable state out of ephemeral sandbox disk by writing to Deta Base, then verify the value survives a redeploy.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Keep durable state out of ephemeral sandbox disk by writing to Deta Base, then verify the value survives a redeploy.
A decision guide for Deta Space Micros comparing managed Base, Drive, and external databases, with schema constraints, trade-offs, and a validation round-trip.
A decision guide for Deta Space apps: compare built-in Space Auth against custom OIDC/JWT stacks, understand sandbox constraints, and validate both paths with the Space CLI.
Deta Base pagination is cursor-based and index-backed. Learn how to page with limit and last, why unindexed queries fail, and when to move to an external Postgres.
Stop fighting with VPCs and connection strings. Learn how Deta Space's Micro architecture simplifies inter-app communication and data persistence for small-scale projects.
Learn how to use Scheduled Actions in Deta Space to run recurring background tasks like database cleanup and API polling without external cron services.
Deta Space moves app state into each user's own cloud folder, inverting the traditional developer-backed tenancy model. This post walks through the trade-offs, an illustrative notes-app example, and how to verify the isolation yourself.
Deta Space shut down in 2024, taking its zero-config Collections store with it. What the per-user design got right, where it hit limits, and what to do with old deta SDK code today.
Context Deta Base fetch() returns a maximum of 1,000 items per call and uses an opaque last cursor for subsequent pages. The cursor is bound to the exact query predicate supplied in the initial call; altering any condition operator or attribute between paginated requests invalidates the cursor and restarts iteration from the beginning. Goal Enable a consumer