All geek questions in one place

Heroku and MongoHQ: use the Heroku plugin or a separate MongoHQ account

I would like to receive the opinion of experienced users. If I use heroku service as a hosting service for my application using MongoDB. Is MongoHQ integration good to use, or maybe it's better to use a standalone MongoHQ account?

I am worried about the following questions:

1) Transferring a database from one application to another (Actully I can not find a guide for this for the MongoHQ plugin for herkou) 2) Migration from Heroku integrated MongoHQ DB into a regular MongoHQ account. (I see no path, expect DB exprot / import) 3) How about connection speed?

Finally, why it may be more responsible for using Heroku and MongoHQ integration than using a stand-alone MongHQ account.

And advise! Thanks!

+4
source share
1 answer

The advantage of using an add-in and integrating with an integrated approach is simply to ease the headache of the configuration. It’s easy to switch from one to the other using something like db.cloneDatabase() .

Heroku addresses essentially just set some environment variables, so don't solve the solution too much, it doesn't really matter if you need to move to a big box (how long does it take to repeat 16/256 MB)?

The problem with the update is that it is not transparent, as with the shard database solution, but the nice part is that it is really easy to do manually.

Hope the answer to your question let me know if you need more information.

+1
source

Source: https://habr.com/ru/post/1384385/

More articles:


All Articles