krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-09-28 07:28:30 +02:00
Code Issues Packages Projects Releases Wiki Activity

Past-tense

Browse Source
This commit is contained in:
Maddie Duhon
2025-03-07 09:21:43 -05:00
parent 6c9db34ec3
commit 76adad5fea
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/blog/case-study-deutsche-telekom.md
+3 -1
View File
@@ -84,7 +84,9 @@ Deutsche Telekom's engineers also cited several standout features that made Qdra
2. **Developer experience**—libraries, multi-language clients, and cross-framework support make integrations seamless.
3. **WebUI & Collection Visualization**—engineers found Qdrant's [built-in collection visualization](https://qdrant.tech/documentation/web-ui/) tools highly useful.
As part of their evaluation, Deutsche Telekom engineers compared multiple solutions, weighing operational simplicity and reliability. One engineer summarized their findings: "Qdrant has way fewer components, compared to the previous solution that required required Kafka, Zookeeper, and only had a hot standby for its index and query nodes. If you rescaled it, you get downtime. Qdrant stays up."
As part of their evaluation, Deutsche Telekom engineers compared multiple solutions, weighing operational simplicity and reliability.
One engineer summarized their findings: "Qdrant has way fewer components, compared to the another that required required Kafka, Zookeeper, and only had a hot standby for its index and query nodes. If you rescale it, you get downtime. Qdrant stays up."
### Scaling AI at Deutsche Telekom & The Future of LMOS