3 ms·
Zep author here. LangChain is a great framework and has a very broad and active ecosystem. Many of LangChain's core components, such as chat history "memory," h
by roseway4 3y ago
Zep author here. LangChain is a great framework and has a very broad and active ecosystem. Many of LangChain's core components, such as chat history "memory," history summarization, entity extraction, vector search, and more, don't scale well in production. They operate in memory and often synchronously within the chat loop, resulting in poor user experiences and limiting deployment options.
You can use third-party ecosystem integrations with external SQL databases, vector databases, etc to fix some of these issues. This requires some know-how, infrastructure, and time. Zep's building blocks are turn-key solutions to these challenges and offered in a single service.
The Zep GitHub project, website, and demo video provide a good overview of the project's functionality and how the service solves these issues.
This blog post on the LangChain website offers some benchmark data using Zep vs LangChain's core memory components: https://blog.langchain.dev/zep-x-langchain-slow-chatbots/ https://blog.langchain.dev/zep-x-langchain-slow-chatbots/
- esafak 3y agoSince you are targeting developers I would highlight the differentiating features: "database-backed", and "asynchronous", or whatever they are. This is more informative than "production-grade", "fast", or "scalable", which anyone can claim. In fact, the competitors have a better claim to being fast -- they're in memory! -- so I would drop them unless I had benchmarks. Something I would also encourage you to work on. Finally, call out your competitors, and explain your value add for each one. Maybe in a table. Why not just use a vector database and hand roll the rest, for example? Good luck!
- roseway4 3y agoThanks for the advice! Some benchmarks here: https://blog.langchain.dev/zep-x-langchain-slow-chatbots/ https://blog.langchain.dev/zep-x-langchain-slow-chatbots/
- verdverm 3y agoThat's not really benchmarks. To me, it just shows why putting things like langchain in the mix makes your life harder in the long run. Having to add more tools is not an ideal solution. What people want are actual "building blocks" that don't require adopting a framework