-
Notifications
You must be signed in to change notification settings - Fork 0
feat/lakebase-cache #13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fjakobs
reviewed
Dec 10, 2025
fjakobs
approved these changes
Dec 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Persistent Cache with Lakebase Support
Summary
This PR introduces a persistent caching layer for Databricks AppKit using Lakebase (PostgreSQL-compatible) as the storage backend, with automatic fallback to in-memory caching when persistent storage is unavailable.
Key Changes
LakebaseConnector: Enterprise-grade PostgreSQL connector with connection pooling, credential rotation, and automatic retry logicCacheManager: Pluggable storage backends supporting both in-memory and persistent (Lakebase) storageFeatures
Cache Manager
getInstanceSync()for easy access after AppKit initializationgetOrExecute()pattern for cache-aside with automatic deduplication of concurrent requestsLakebase Connector
Configuration Options
Architecture
Test Plan
CacheManager(34 tests)InMemoryStorage(18 tests)PersistentStorage(27 tests)LakebaseConnector(32 tests)Breaking Changes
None. The cache is automatically initialized by AppKit with sensible defaults.
Environment Variables
For persistent cache (Lakebase):
Expected env vars when you add lakebase resource to an databricks app
Or via connection string:
Dependencies Added
pg(^8.16.3) - PostgreSQL client@types/pg(^8.15.6) - TypeScript definitions