IntegrationIntermediatesoapmetadatacaching
Implement SOAP describeGlobal caching for metadata-heavy integrations
Real World Scenario
Dynamic SOAP integration calls describeGlobal and describeSObjects on every batch adding 30 seconds overhead per run.
Expected Answer
• Cache describe results 24 hours in middleware or Platform Cache
• Invalidate cache on Salesforce metadata deploy webhook
• Tooling API Metadata SOAP for targeted describe not full global
• Schema version pin integration to known API version
• Warm cache on integration startup not per transaction
• Document cache TTL tradeoff stale field detection delay
• Migrate dynamic describe to compile-time mapping where possible
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Stay within limits by: Cache describe results 24 hours in middleware or Platform Cache. Bulkify everything — never query or DML in loops. Tooling API Metadata SOAP for targeted describe not full global. describeGlobal per batch is anti-pattern—cache schema at integration boundary. Balance speed of delivery with maintainability.
Architect Perspective
describeGlobal per batch is anti-pattern—cache schema at integration boundary.