The current LangChian approach is framework-oriented, which treats frameworks themselves as the central part of the system and databases as a sub-part of the system.
This gives a higher level of abstraction but a lower level of flexibility because we will have less database-like operation, which has more flexibility.
This is one of the main reasons why people are complaining about the complexity of LangChain despite its intentions of making development easier.
What we end up developing internally for our own front end is a more database-oriented solution. We basically implemented the embedding and indexing functionality directory on top of MongoDB and Pinecone, making it look like a MongoDB with a built-in async embedding pipeline. The reason why we chose to do this is because we wanted to keep database-like syntax that is as powerful as LangChian.
What do you guys think? And what is your solution for your apps?
This is one of the main reasons why people are complaining about the complexity of LangChain despite its intentions of making development easier.
What we end up developing internally for our own front end is a more database-oriented solution. We basically implemented the embedding and indexing functionality directory on top of MongoDB and Pinecone, making it look like a MongoDB with a built-in async embedding pipeline. The reason why we chose to do this is because we wanted to keep database-like syntax that is as powerful as LangChian.
What do you guys think? And what is your solution for your apps?