Skip to content

Commit 60f7685

Browse files
authored
Comparison table (#640)
* Adding anchors * Feature comparison table * Update table to rm unneeded row * remove en-us in links
1 parent b2d8788 commit 60f7685

File tree

1 file changed

+19
-1
lines changed

1 file changed

+19
-1
lines changed

README.md

Lines changed: 19 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@ If you already have existing Azure resources, you can re-use those by setting `a
144144
1. Run `azd env set AZURE_SEARCH_SERVICE_RESOURCE_GROUP {Name of existing resource group with ACS service}`
145145
1. If that resource group is in a different location than the one you'll pick for the `azd up` step,
146146
then run `azd env set AZURE_SEARCH_SERVICE_LOCATION {Location of existing service}`
147-
1. If the search service's SKU is not standard, then run `azd env set AZURE_SEARCH_SERVICE_SKU {Name of SKU}`. ([See possible values](https://learn.microsoft.com/en-us/azure/templates/microsoft.search/searchservices?pivots=deployment-language-bicep#sku))
147+
1. If the search service's SKU is not standard, then run `azd env set AZURE_SEARCH_SERVICE_SKU {Name of SKU}`. ([See possible values](https://learn.microsoft.com/azure/templates/microsoft.search/searchservices?pivots=deployment-language-bicep#sku))
148148

149149
#### Other existing Azure resources
150150

@@ -320,6 +320,24 @@ The primary differences:
320320
* This repository includes multiple RAG (retrieval-augmented generation) approaches that chain the results of multiple API calls (to Azure OpenAI and ACS) together in different ways. The other repository uses only the built-in data sources option for the ChatCompletions API, which uses a RAG approach on the specified ACS index. That should work for most uses, but if you needed more flexibility, this sample may be a better option.
321321
* This repository is also a bit more experimental in other ways, since it's not tied to the Azure OpenAI Studio like the other repository.
322322

323+
Feature comparison:
324+
325+
| Feature | azure-search-openai-demo | sample-app-aoai-chatGPT |
326+
| --- | --- | --- |
327+
| RAG approach | Multiple approaches | Only via ChatCompletion API data_sources |
328+
| Vector support | ✅ Yes | ✅ Yes |
329+
| Data ingestion | ✅ Yes (PDF) | ✅ Yes (PDF, TXT, MD, HTML) |
330+
| Persistent chat history | ❌ No (browser tab only) | ✅ Yes, in CosmosDB |
331+
332+
Technology comparison:
333+
334+
| Tech | azure-search-openai-demo | sample-app-aoai-chatGPT |
335+
| --- | --- | --- |
336+
| Frontend | React | React |
337+
| Backend | Python (Quart) | Python (Flask) |
338+
| Vector DB | Azure Cognitive Search | Azure Cognitive Search |
339+
| Deployment | Azure Developer CLI (azd) | Azure Portal, az, azd |
340+
323341
</details>
324342

325343
<details><a id="switch-gpt4"></a>

0 commit comments

Comments
 (0)