|
You are here |
dolthub.com | ||
| | | | |
tanelpoder.com
|
|
| | | | | Disclaimer: I'm not an ML expert and not even a serious ML specialist (yet?), so feel free to let me know if I'm wrong! It seems to me that we have hit a bit of an "on-premises" vs. "on-premise" situation in the ML/AI and vector search terminology space. The majority of product announcements, blog articles and even some papers I've read use the term vector embeddings to describe embeddings, but embeddings already are vectors themselves! - Linux, Oracle, SQL performance tuning and troubleshooting training & writing. | |
| | | | |
electric-sql.com
|
|
| | | | | Local AI with Postgres, pgvector and llama2, running inside a Tauri app with realtime sync powered by ElectricSQL This is the architecture of the future! | |
| | | | |
www.ethanrosenthal.com
|
|
| | | | | Spoiler alert: the answer is maybe! Although, my inclusion of the word "actually" betrays my bias. Vector databases are having their day right now. Three different vector DB companies have raised money on valuations up to $700 million (paywall link). Surprisingly, their rise in popularity is not for their "original" purpose in recommendation systems, but rather as an auxillary tool for Large Language Models (LLMs). Many online examples of combining embeddings with LLMs will show you how they store the em... | |
| | | | |
www.mattblodgett.com
|
|
| | | Matt Blodgett on topics occasionally germane to software development. | ||