Composite Storage - use different storage adapters for diff primitives

[abhiaiyer91]

Couple things happening in here to set the stage for future changes.

1. MastraCompositeStorage

This takes existing storage adapters and allows the user to create a composite of them by delegating different primitives to different storage adapters.

new MastraCompositeStorage({ stores: { traces: new LibSQLStore(), conversations: new PostgresStore() } })

2. Domain specific storage interfaces

Introduce interfaces for each domain

{
    traces: MastraTracesStorage;
    conversations: MastraConversationsStorage;
    workflows: MastraWorkflowsStorage;
    scores: MastraScoresStorage;
  };

This would allow Storage adapters to implement the relevant piece instead of all if irrelevant.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[changeset-bot]

⚠️ No Changeset found

Latest commit: 86c313f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
assistant-ui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 12, 2025 7:02am
mastra-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 12, 2025 7:02am
openapi-spec-writer	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 12, 2025 7:02am

[greptile-apps]

PR Summary

Introduces a composite storage adapter that enables using different storage backends for distinct data types, allowing for optimized storage strategies per data category.

• Added packages/core/src/storage/composite.ts implementing MastraCompositeStorage that routes operations to specialized storage adapters based on data type (traces, conversations, workflows, scores)
• Modified packages/core/src/storage/base.ts to remove deprecated static table names and improve method signatures for better integration with composite storage
• The implementation allows mixing storage backends (e.g., using Redis for traces while keeping conversations in PostgreSQL) for performance optimization

_{3 files reviewed, 2 comments
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

logic: Unreachable code: Error thrown after return statement

Suggested change

	throw new Error(
	`Resource working memory is not supported by this storage adapter (${this.constructor.name}). ` +
	`Supported storage adapters: LibSQL (@mastra/libsql), PostgreSQL (@mastra/pg), Upstash (@mastra/upstash). ` +
	`To use per-resource working memory, switch to one of these supported storage adapters.`,
	);
	return this.#stores.conversations.updateResource(_);

[greptile-apps]

style: getTraces return type should be Trace[] instead of any[]

Suggested change

	async getTraces(args: StorageGetTracesArg): Promise<any[]> {
	return this.#stores.traces.getTraces(args);
	}
	async getTraces(args: StorageGetTracesArg): Promise<Trace[]> {
	return this.#stores.traces.getTraces(args);
	}