Should this project be renamed?

[Hixon10]

If this solution becomes popular, it will be really hard to google for something because of another database with the same name - https://aws.amazon.com/documentdb/

[safern]

cc: @abinav2307

[takekazuomi]

Thanks for the great project.

This is a document database extension of Postgres, not a database itself, so it shouldn't be confused with aws documentdb.

If you were to rename it, I think pgdocument would be a good choice, like pgvector.

A little off topic, but...

When I first heard about documentdb, I mistakenly thought that Cosmos DB had become OSS. Documentdb was the old name for Cosmos DB.

[pjmlp]

Using the name of a well establish product AWS DocumentDB, reminds me of the issues in the past of calling Microsoft SQL Server as is, given its origin as collaboration with Sybase and their SQL Server product.

Conflicting names on the same business area always lead to confusion about which product is being talked about and hinder adoption.

[bburns]

Yeah, is this name collision intentional? Seems pretty strange...

[abinav2307]

@bburns not necessarily intentional but the bigger picture goal was to leverage Postgres for optimizing the document database experience, so we decided on this name.

[abinav2307]

To add - documentdb is an industry accepted abbreviation for a "document database", a class of databases. Microsoft (in 2014), Amazon (in 2018) and many other companies used this name as part of their products with this precise meaning. This project with the pg_documentdb extension makes PostgreSQL a document database. We felt (and remain convinced) a simple descriptive name capturing just that is best for this extension.

[bsherwin]

If this solution becomes popular, it will be really hard to google for something because of another database with the same name - https://aws.amazon.com/documentdb/

DocumentDB was an Azure thing before it was AWS...
https://azure.microsoft.com/en-us/blog/what-s-new-with-documentdb

[dror-g]

@bburns not necessarily intentional but the bigger picture goal was to leverage Postgres for optimizing the document database experience, so we decided on this name.

Oddly enough, AWS DocumentDB is also based on Postgres.

And by the way - it's terrible.
Slow queries aside, the worst thing is storage bloat.
No compact command, and apparently not vacuuming Postgres either..