krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-10-05 10:58:32 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update case-study-trustgraph.md

Browse Source
This commit is contained in:
daniel-azoulai
2025-10-08 14:59:51 -07:00
parent dbeef58143
commit 6ab5acb863
1 changed files with 1 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/blog/case-study-trustgraph.md
+1 -3
View File
@@ -30,8 +30,6 @@ But as soon as those demos face enterprise requirements — constant data ingest
This is exactly the gap TrustGraph set out to close. From day one, they designed their platform for **availability, determinism, and scale** — with Qdrant as a core piece of the architecture.
###
![Failure mode map — “From POC to production](/blog/case-study-trustgraph/failure-map-poc-to-production.png)
*Failure mode map — “From POC to production.”*
@@ -105,7 +103,7 @@ By combining a resilient streaming backbone, graph-native semantics, and Qdrant-
* **Developer Simplicity** — Qdrant’s open-source, containerized design makes scaling straightforward and reduces operational friction.
“We haven’t had a reason to revisit alternatives. Qdrant checks the boxes for speed, reliability, and simplicity—and it keeps doing so.”
*“We haven’t had a reason to revisit alternatives. Qdrant checks the boxes for speed, reliability, and simplicity—and it keeps doing so.”*
— *Daniel Davis, Co-founder, TrustGraph*
## **From Demos to Durable Infrastructure**