Yes - this and to make it easier to understand how you'd use Pinecone at scale.
We get a lot of feedback that our many open-source Jupyter notebooks (github.com/pinecone-io/examples) are very helpful for learning new techniques and understanding how patterns work - even for starting new applications.
However, we're also often asked how to go from Notebook to prod. The Reference Architecture is a step in the direction of making this easier and more clear.
Comments
Sounds silly to go to a vector DB vendor to get reference architecture for my app where it will only be a small part of my app.
I believe the point is that you can leverage the reference architecture for that small part of your app.
Yes - this and to make it easier to understand how you'd use Pinecone at scale.
We get a lot of feedback that our many open-source Jupyter notebooks (github.com/pinecone-io/examples) are very helpful for learning new techniques and understanding how patterns work - even for starting new applications.
However, we're also often asked how to go from Notebook to prod. The Reference Architecture is a step in the direction of making this easier and more clear.