3 ms·
This is the case where author has a fixed story and then filled rest of the details with good sounding sentences. > Have a problem with PostgreSQL? Pop it into
by YetAnotherNick 3y ago
This is the case where author has a fixed story and then filled rest of the details with good sounding sentences.
> Have a problem with PostgreSQL? Pop it into a search engine and you'll get an answer right away. But have a problem with a vector DB? Comb the GitHub Issues or Discord and hope that you find an answer
> They often have great ecosystems around them
> They use well-known concepts
PostgreSQL issues are generally significantly harder to debug than vector db in my experience. In general, a lot of times I found documentation and concepts to be significantly better for quite a bit of newer technologies like tailwind, caddy, gin, golang than say springboot or react or oracle DB or C++ or cassandra. Comparing PostgreSQL to graph DB or vector DB is very apples to oranges as one can't replace other.
Telling old is better than new in general is both wrong and harmful to software engineering.
- mplewis 3y agoBut this is empirically true, I’m not sure what your issue is with the statement? The likelihood you will run into a serious undocumented issue with Postgres is so much lower than with some new vector database. I’ve personally experienced this moving between the mature Rails ecosystem and multiple immature microservice frameworks.
- YetAnotherNick 3y agoAs I said comparing postgres to vector db is weird example as one is not replacement of other and one field is going more technological shift. Better example would be comparing say apache to caddy or spring boot to gin or even oracle nosql to mongo.