There are competing implementations of MongoDB's API. Microsoft's CosmosDB is promising but, last I tried it, not complete enough for Apostrophe. AWS DocumentDB may be up to the task, if the plaintext search indexing features of Apostrophe were replaced with an alternative.
In the meantime, PostgreSQL has perfectly good querying capabilities, including for JSON if you need schemaless data for some reason, working full-text search, and (unlike MongoDB's API design) an injection-resistant query API.
What's the point of continuing to pour engineering resources into something that doesn't actually improve upon what's already available?
MongoDB supports indexing of nested and array properties and has a 16MB document size limit for BSON documents. Those things help a lot in a CMS; if you prettyprint an Apostrophe page in MongoDB the structure just pops out at you.
We've had good experiences hosting it both with the community edition and with Atlas. When your documents make up a page tree and have a lot of structure within each document that would otherwise involve extra joins, it's a nice representation and we really haven't paid a price for using it. If we had, we might have made other choices. YMMV.
Comments
There are competing implementations of MongoDB's API. Microsoft's CosmosDB is promising but, last I tried it, not complete enough for Apostrophe. AWS DocumentDB may be up to the task, if the plaintext search indexing features of Apostrophe were replaced with an alternative.
In the meantime, PostgreSQL has perfectly good querying capabilities, including for JSON if you need schemaless data for some reason, working full-text search, and (unlike MongoDB's API design) an injection-resistant query API.
What's the point of continuing to pour engineering resources into something that doesn't actually improve upon what's already available?
MongoDB supports indexing of nested and array properties and has a 16MB document size limit for BSON documents. Those things help a lot in a CMS; if you prettyprint an Apostrophe page in MongoDB the structure just pops out at you.
We've had good experiences hosting it both with the community edition and with Atlas. When your documents make up a page tree and have a lot of structure within each document that would otherwise involve extra joins, it's a nice representation and we really haven't paid a price for using it. If we had, we might have made other choices. YMMV.