Show HN: I built a vector database API on Cloudflare
1–10 of 30 posts
Re: Show HN: I built a vector database API on Cloudflare
#2Cool project, I look forward to digging in a bit - been meaning to check out some of cloudflare's dev offerings for a bit.
Athena is already a name in the cloudy database segment though - Amazon's managed Presto offering
Re: Show HN: I built a vector database API on Cloudflare
#3Cool project, I look forward to digging in a bit - been meaning to check out some of cloudflare's dev offerings for a bit. Athena is already a name in the cloudy database segment though - Amazon's managed Presto offering https://docs.aws.amazon.com/athena/latest/ug/what-is.html
Came here to say this.
Very cool project but unfortunately the name is immediately a trademark issue.
Re: Show HN: I built a vector database API on Cloudflare
#4Cool project, I look forward to digging in a bit - been meaning to check out some of cloudflare's dev offerings for a bit. Athena is already a name in the cloudy database segment though - Amazon's managed Presto offering https://docs.aws.amazon.com/athena/latest/ug/what-is.html
Came here to say this. Very cool project but unfortunately the name is immediately a trademark issue.
Indeed. Athena is a pretty popular database service and is trademarked by AWS:
https://aws.amazon.com/trademark-guidelines/
I would expect a cease and desist at some point.
Re: Show HN: I built a vector database API on Cloudflare
#5Earlier quoted context omitted.
Came here to say this. Very cool project but unfortunately the name is immediately a trademark issue.
Indeed. Athena is a pretty popular database service and is trademarked by AWS: https://aws.amazon.com/trademark-guidelines/ I would expect a cease and desist at some point.
Yeah, came here to say this, you’ll probably have problems with Amazon’s trademarked Athena database offering.
Re: Show HN: I built a vector database API on Cloudflare
#6Earlier quoted context omitted.
Indeed. Athena is a pretty popular database service and is trademarked by AWS: https://aws.amazon.com/trademark-guidelines/ I would expect a cease and desist at some point.
Yeah, came here to say this, you’ll probably have problems with Amazon’s trademarked Athena database offering.
Indubitably, there might (p > 0.85) be an issue with the managed Presto database offered by Amazon, which is also named Athena btw.
Re: Show HN: I built a vector database API on Cloudflare
#7Earlier quoted context omitted.
Came here to say this. Very cool project but unfortunately the name is immediately a trademark issue.
Indeed. Athena is a pretty popular database service and is trademarked by AWS: https://aws.amazon.com/trademark-guidelines/ I would expect a cease and desist at some point.
The page says they hold the trademark to “Amazon Athena”. Does this come into conflict with a project named “AthenaDB”?
Re: Show HN: I built a vector database API on Cloudflare
#8One thing I can confirm from this code is that unlike what I previously thought vector search is not the main point of a vector database, rather it's read, write, update crud, just like normal SQL databases, with the exception that data are vector data instead of text and numbers.
Re: Show HN: I built a vector database API on Cloudflare
#9It's a stretch to call this building a vector database when this is just an API over Cloudflare's distributed database offerings.
This also uses a fixed embedding which will not be compatible with all machine learning projects that people will want to use a vector database for. The chosen embedding only supports text so making an image search for example wouldn't be possible to do.
Re: Show HN: I built a vector database API on Cloudflare
#10Earlier quoted context omitted.
Indeed. Athena is a pretty popular database service and is trademarked by AWS: https://aws.amazon.com/trademark-guidelines/ I would expect a cease and desist at some point.
The page says they hold the trademark to “Amazon Athena”. Does this come into conflict with a project named “AthenaDB”?
Even if you avoid legal issues, there's still the practical issues.
Fighting for ranking on Google. Conflicting tags on stackoverflow. Confused users sending you complaints about someone else's product. And so on.