We are definitely not going to require Atlas for running our tests, so the search feature is useless at this moment.

Dear Mongodb Team, Pls allow to run your enterprise mongodb locally or docker.

Nobody asks to share source code and lots of clients are using your cloud to deal with mongodb anyway so there is no financial risk.

Also it will bring more clients to use your cloud solution. You shouldn't care if some developers run enterprise mongodb on their servers because at the end they will come to you. The same story happened to MySql so pls don't be silly.

Any update on this?

Clarification on those available features would be helpful.

It is very hard to work without local support of same functionality. It makes you think if next solutions will be created with mongodb as it does not correspond with functionality that is in cloud and on-prem.

We would love to use Atlas Search for our application but the lack of being able to run an equivalent aggregation stage locally, this feature is completely useless for us. Not being able to test features like e.g. data exports from user filtered lists powered by Atlas Search locally is an absolute showstopper - not to mention the inability to integrate with testing....

I work for two companies where MongoDB Atlas is used. We are also not using Search just because of the missing possibility to use it during local development & CI.

I agree with all the previous comments.
Without being able to develop locally, Atlas Search will not be a possibility

For lost of dev teams (if we summarize), dev cycle is this :

Local dev & testing => CI => Production

Not being able to dev & test locally and setup proper CI puts a lot of risk and stress on any team using the feature in production.

This approach cannot scale.

Sorry to be blunt, but keep it that way, and this feature stay a technological feat of strength that can't reach it's full potential for the lack of understanding of customer's needs.

"We have a number of features that can make mostly-local development easier. Please let us know if you have questions."

What kind of features are this? Without local support for development purposes, i don't see that we will be using this feature on prod on atlas.

Hi, you said: "We have a number of features that can make mostly-local development easier. Please let us know if you have questions."

what features? how can I let you know about my questions?

I understand you want to keep it a power feature of using atlas, but can't you at least build a limited on premisse solution for testing and in development usage?

Just because of this we have to maintain elastic search along with mongodb. :(

We really need this feature as well. Not being able to run it locally means we can't fully move over parts of our system to using it.

We really need this feature for our development as well, having this only available remotely blocks us from using proper automated tests and it slows down local development.

We need this feature in an on-premises solution. We have a quick search in our application that scans fields like first name, last name, date of birth, street, zip code, etc.. A text index is perfect for this. But when the user enters something into the quick search, the results should be displayed immediately. For this use case we need the possibility to search for prefixes, too.

Unfortunately this feature is only available in Atlas. However, this feature is very important for our application. Due to Google and co this kind of search is expected by our customers.

We would appreciate it very much if this feature would be available on-prem, too.

For local testing, be sure to follow and vote on https://feedback.mongodb.com/forums/924868-atlas-search/suggestions/38786779-allow-the-ability-to-test-atlas-search-locally

At this time we still have no plan to support Atlas Search for on-prem installations--however it is a common enough request that this idea will remain open to gather further input from the community.

Two major areas: not being able to test locally is HUGE. Also, full dependency on Atlas, is also bad, since some clients do not want to use Atlas.

While we're not running this on-prem but within atlas, not being able to test things locally or in unit tests is a pretty big downer.