LWCIntermediatewireldsperformance
Compose multiple @wire adapters without duplicate server round trips
Real World Scenario
Record page child LWCs each wire getRecord on same Account Id causing redundant server calls and slow paint.
Expected Answer
• Parent provider LWC wires once passes record via @api to children
• LDS deduplicates identical wire requests in same page session
• Consolidate related data fetches into single GraphQL wire if UI API supports
• Avoid imperative getRecord duplicate when wire already loaded
• Lazy wire second adapter only when user expands section
• Monitor network tab in UAT counting duplicate getRecord calls
• LMS broadcast record context alternative for loosely coupled siblings
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Stay within limits by: Parent provider LWC wires once passes record via @api to children. Bulkify everything — never query or DML in loops. Consolidate related data fetches into single GraphQL wire if UI API supports. Duplicate wires are architecture smell—parent provider or LMS before micro-LWC proliferation. Balance speed of delivery with maintainability.
Architect Perspective
Duplicate wires are architecture smell—parent provider or LMS before micro-LWC proliferation.