Skip to content

Rename "managed database" to "instant database" in docs - #10

Merged
eddietejeda merged 1 commit into
mainfrom
instant-databases-rename
Aug 25, 2026
Merged

Rename "managed database" to "instant database" in docs#10
eddietejeda merged 1 commit into
mainfrom
instant-databases-rename

Conversation

@eddietejeda

Copy link
Copy Markdown
Contributor

Updates user-facing prose (README, DESIGN, and module docstrings) to use the new product term "instant database" instead of "managed database". In doc code examples only comments were touched.

Code identifiers, API names, and wire-format values intentionally keep managed — this is a wording-only change. Historical changelog entries are left as-is.

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wording-only change. Identifiers, API names, and CHANGELOG history are correctly left alone.

nit: two occurrences of the old term were missed in DESIGN.md because they wrap across lines, so a single-line search does not catch them. Not blocking.

  • DESIGN.md:47-48 -- 'a small managed / database in HotData'
  • DESIGN.md:150-151 -- 'a query executes within one managed / database'

Both are the same user-facing prose this PR is renaming. Line 47 in particular describes the registry, which README:157 and registry.py:1 now call an instant database.

super nit: tests/fakes.py:3 also uses the old term. Test-internal, so leaving it is defensible. Not blocking.

@eddietejeda
eddietejeda merged commit a6ece84 into main Aug 25, 2026
3 checks passed
@eddietejeda
eddietejeda deleted the instant-databases-rename branch August 25, 2026 03:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant