Please support on-prem installations
Can we get Search on-prem? Is this always going to be an Atlas-only feature?
![](https://secure.gravatar.com/avatar/04dc793848171fe85e58606f21af9aa2?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)
As it stands today, we are not planning to support on-premise. Maintaining a single deployment model allows us to quickly deliver features to support more and more customers’ workloads with a leading search engine that is an improvement on predecessors. Atlas Search is Atlas-only for now.
We have a number of features that can make mostly-local development easier. Please let us know if you have questions.
-
רז בוכניק commented
Why not develop and perform CI tests against remote cloud databases? Why is it a big issue at all if can I ask..
-
Emilio commented
A similar feature is now available in preview status:
-
Justus Voigt commented
this is a joke. How is this to any use when you can't test it in local development?
-
Andrii Nyzhnyk commented
Dear Mongodb Team, all of us kindly ask you to add this feature to the community edition. This feature does not make sense if it is available only on the Atlas without the possibility of running it locally during feature development. We have used the Atlas for production and development stages for years but now we need a trusted solution for full-text search out of the box.
-
Dan commented
The impossibility to use full text search on prem with mongodb is one of the reason we switched to another database software. You waited two years (yes, TWO YEARS !!!) to announce that a full text search capability will never be available on prem, while customers, like us, used your technologies for their backend and were waiting for them to be available locally. By making full text search - and apparently your future services as well - only available through your managed solution, is a vendor lock-in attempt and prevent many businesses to choose your solution.
After uncountables headaches trying to synchonize mongodb with elasticsearch, we finally looked at two other solutions, offering JSON data structures support and full text search capabilities on prem from the get-go: CouchDB and Redis. We finally switched to Redis, which has a better integration of services.
Making some features unavailable on prem was a bad move, and may have a negative impact in the long run. We can't trust your company anymore with that kind of strategy in mind. A managed service suits better some companies, especially when they have to manage data across many countries. But others need to have full control on their data, and some can't afford to start with a managed service, and need to start locally. By not keeping both solutions on par with the features you propose, you are keeping away a large part of your user base. -
songjie commented
Move to postgresql
-
Antony commented
This completely prevents local development or testing, thus makes MongoDB unsuitable for robust production applications.
-
Andrew commented
Is it possible to reopen this request?
-
Daniel commented
We are definitely not going to require Atlas for running our tests, so the search feature is useless at this moment.
-
vadim sadykhov commented
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.
-
Rohan Sapkal commented
Any update on this?
-
Andrew commented
Clarification on those available features would be helpful.
-
Igoris commented
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.
-
Stephan commented
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....
-
Václav commented
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.
-
Ruben commented
I agree with all the previous comments.
Without being able to develop locally, Atlas Search will not be a possibility -
Samuel Rossille commented
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.
-
Nils commented
"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.
-
Eshel commented
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?
-
Bruno commented
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?