Store-to-store interaction in Vue - Performance & Optimization

Performance: Store-to-store interaction

MEDIUM IMPACT

This affects how quickly and efficiently state changes propagate between different stores, impacting UI responsiveness and rendering speed.

Sharing state updates directly between two Vue stores

Vue

import { useStoreA } from './storeA';
import { useStoreB } from './storeB';
import { watch } from 'vue';

const storeA = useStoreA();
const storeB = useStoreB();

watch(() => storeA.sharedState, (newVal) => {
  storeB.sharedState = newVal;
});

Using Vue's watch API batches updates and avoids unnecessary immediate re-renders.

📈 Performance GainReduces reflows to a single batch per update cycle, improving interaction speed.

Sharing state updates directly between two Vue stores

Vue

import { useStoreA } from './storeA';
import { useStoreB } from './storeB';

const storeA = useStoreA();
const storeB = useStoreB();

storeA.$subscribe(() => {
  storeB.sharedState = storeA.sharedState;
});

Direct subscription causes storeB to update on every storeA change, triggering multiple re-renders and reflows.

📉 Performance CostTriggers 1 reflow per storeA update, causing slower UI responsiveness.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Direct store subscription	Multiple reactive updates	Multiple reflows per update	High paint cost due to layout thrashing	[X] Bad
Using Vue watch for syncing stores	Single reactive update batch	Single reflow per update cycle	Lower paint cost with batched layout	[OK] Good

Rendering Pipeline

When one store updates another directly, Vue triggers reactive updates causing style recalculation, layout, and paint. Excessive direct updates cause repeated layout thrashing.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckLayout due to repeated reflows from multiple reactive updates

Core Web Vital Affected

INP

This affects how quickly and efficiently state changes propagate between different stores, impacting UI responsiveness and rendering speed.

Optimization Tips

1Avoid direct store-to-store subscriptions that cause immediate reactive updates.

2Use Vue's watch or computed properties to batch and control state syncing.

3Monitor layout thrashing in DevTools to catch inefficient store interactions early.

Performance Quiz - 3 Questions

What is a common performance issue with direct store-to-store subscriptions in Vue?

A They reduce bundle size significantly.

B They cause multiple reflows and slow UI responsiveness.

C They improve Largest Contentful Paint (LCP).

D They eliminate the need for reactive state.

DevTools: Performance

How to check: Record a performance profile while interacting with the app. Look for frequent layout and paint events triggered by store updates.

What to look for: Multiple layout thrashing events indicate inefficient store-to-store updates; fewer, batched layout events indicate good performance.

Practice

1. What is the main purpose of store-to-store interaction in Vue's Pinia stores?

easy

A. To create multiple independent stores without any connection

B. To allow one store to access or call actions from another store

C. To replace Vue components with stores

D. To automatically sync stores with a backend database

Solution

1. Step 1: Understand store-to-store interaction

   Store-to-store interaction means one store can use another store's state or actions to share data or trigger updates.

2. Step 2: Identify the purpose

   This interaction helps keep data consistent by letting stores communicate, not by replacing components or syncing automatically.

3. Final Answer:

   To allow one store to access or call actions from another store -> Option B

4. Quick Check:

   Store-to-store interaction = Access other store's actions/state [OK]

Hint: Remember: stores talk by calling each other's actions [OK]

Common Mistakes:

• Thinking stores replace components
• Assuming stores sync automatically with backend
• Believing stores are always independent

2. Which of the following is the correct way to use one Pinia store inside another in Vue 3?

easy

A. const storeA = useStoreA(); const storeB = useStoreB(); import { useStoreA } from './storeA';

B. import useStoreA from './storeA'; const storeB = useStoreB();

C. const storeA = useStoreB(); const storeB = useStoreA();

D. import { useStoreA } from './storeA'; const storeB = useStoreB(); const storeA = useStoreA();

Solution

1. Step 1: Import the store function before usage

   You must import the store function (e.g., useStoreA) before calling it to get the store instance.

2. Step 2: Call the store functions to get instances

   Call useStoreA() and useStoreB() to get their store instances for interaction.

3. Final Answer:

   import { useStoreA } from './storeA'; const storeB = useStoreB(); const storeA = useStoreA(); -> Option D

4. Quick Check:

   Import then call stores = correct syntax [OK]

Hint: Always import store before calling useStore() [OK]

Common Mistakes:

• Calling useStore before importing
• Mixing store names when calling
• Incorrect import syntax without braces

3. Given these two Pinia stores, what will be the console output after calling storeB.incrementA()?

const useStoreA = defineStore('A', {
  state: () => ({ count: 0 }),
  actions: { increment() { this.count++ } }
});

const useStoreB = defineStore('B', {
  actions: {
    incrementA() {
      const storeA = useStoreA();
      storeA.increment();
      console.log(storeA.count);
    }
  }
});

const storeB = useStoreB();
storeB.incrementA();

medium

A. 1

B. 0

C. undefined

D. Error: useStoreA is not defined

Solution

1. Step 1: Understand storeA initial state and increment

   storeA starts with count = 0. Calling increment() increases count by 1.

2. Step 2: Trace incrementA action in storeB

   incrementA calls storeA.increment(), then logs storeA.count which is now 1.

3. Final Answer:

   1 -> Option A

4. Quick Check:

   Increment count from 0 to 1, then log 1 [OK]

Hint: Calling other store's action updates its state immediately [OK]

Common Mistakes:

• Assuming count stays 0 after increment
• Thinking console logs undefined
• Forgetting to call useStoreA inside action

4. What is wrong with this code snippet trying to use storeA inside storeB?

const useStoreA = defineStore('A', {
  state: () => ({ value: 10 })
});

const useStoreB = defineStore('B', {
  actions: {
    updateValue() {
      const storeA = useStoreA;
      storeA.value = 20;
    }
  }
});

medium

A. defineStore cannot be used inside actions

B. Cannot assign value directly to storeA.value

C. useStoreA is not called as a function, so storeA is not a store instance

D. State must be a function returning an object

Solution

1. Step 1: Check how useStoreA is used inside updateValue

   useStoreA is referenced without parentheses, so storeA is a function reference, not a store instance.

2. Step 2: Understand consequences of missing parentheses

   Without calling useStoreA(), you cannot access or modify state like storeA.value.

3. Final Answer:

   useStoreA is not called as a function, so storeA is not a store instance -> Option C

4. Quick Check:

   Call useStoreA() to get store instance [OK]

Hint: Always call useStore() with () to get the store [OK]

Common Mistakes:

• Forgetting parentheses when calling useStore
• Trying to assign state directly without actions
• Misunderstanding defineStore usage

5. You have two stores: useCartStore managing cart items and useUserStore managing user info. You want to clear the cart when the user logs out. How should you implement this store-to-store interaction inside useUserStore?

hard

A. Inside the logout action, call const cart = useCartStore(); cart.clearItems();

B. Emit an event from useUserStore and listen in useCartStore to clear items

C. Directly modify useCartStore state without calling its actions

D. Reset useUserStore state and expect useCartStore to reset automatically

Solution

1. Step 1: Identify the correct way to trigger cart clearing

   Calling useCartStore() inside useUserStore's logout action gets the cart store instance.

2. Step 2: Use cart store's action to clear items

   Calling cart.clearItems() properly updates the cart state in a controlled way.

3. Final Answer:

   Inside the logout action, call const cart = useCartStore(); cart.clearItems(); -> Option A

4. Quick Check:

   Call other store's action inside logout to clear cart [OK]

Hint: Call other store's action inside your store's action [OK]

Common Mistakes:

• Trying to modify other store's state directly
• Using events instead of direct store calls
• Expecting automatic reset without explicit calls