>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3477368. --> Reported by: [scott_euser](https://www.drupal.org/user/3267594) Related to !108 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Much of the heavy lifting is currently done in Search API Backend plugin yet is quite Milvus/Zilliz specific. Move it away into VDB Providers interfaces/base class to allow different VDB Providers sufficient control.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>Attempting to do Pinecone <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/ai/issues/3470417" title="Status: Closed (fixed)">#3470417: Provide integration with Pinecone</a></span> revealed this; however, similar problems would happen for any VDB Provider</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Refactor to allow other VDB Providers</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>MR coming</p> <h3 id="summary-ui-changes">User interface changes</h3> <p>VDB Providers can provide their own settings for the search api backend</p> <h3 id="summary-api-changes">API changes</h3> <p>N/A</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>Interfaces changed within AI Search</p>