All geek questions in one place

What delay can I expect when using MongoHQ from an external web server

Does anyone have any advice regarding using a solution for hosted databases, in particular MongoDB, with a web server. In particular:

Is latency acceptable? How can I localize (geographically through Azure, etc.) a web server with a hosted database server to reduce latency? Is there a way to reduce the cost of bandwidth from making a call from a web server to a hosted database server (via a private IP or another?) Are there any web hosting solutions offering a package (hosting applications and hosted databases)

+4
source share
1 answer

I just looked at MongoHQ - I see no way to specify a specific data center. Even if you could (maybe I skipped this part), these are AWS regions that do not live in the same data centers as Windows Azure. You should consider which AWS area is closest, for example, to the Windows Azure North Central data center.

If you want to reduce bandwidth / latency, you can place MongoDB as a worker or even as a website that hosts your website, which will reduce the monthly cost of an instance. Just remember that if you host Azure on Windows, you should be prepared to scale, so stand-alone MongoDB databases will not be enough. Well, you could put MongoDB in your working role, store your database on Cloud Drive (in the blob repository) to ensure longevity and ensure that you never raise the instance count beyond 1. If only one instance works, you can have intermittent shutdowns when the working role is rebooted to install a security patch or equipment malfunction (you must be backed up in a very short time, but you will have periodic periods of the database offline).

I [demonstrated using MongoDB replicasets] [1] at the MongoSV conference. The only problem is that for this you need 3 instances. If you usually run 3 instances of your web role, you can copy them to these instances. Otherwise, you will need to manage this configuration in a separate set of work roles. Compared to MongoHQ, your monthly expenses will increase (but your bandwidth will not be charged between your web role and MongoDB, you will have very low latency and you can easily scale your database to 1 TB, beyond the MongoHQ limit of 2GB.

One more thing. If you have several sites using MongoDB, you can create a single service hosted in MongoDB in Windows Azure (as described above), and then access it from all deployments of your website. This will give you economies of scale by reducing the cost of migrating to a MongoDB database with multiple tenants.

EDIT 6/16/2013 This is a very old, outdated answer. Several updates:

  • Both MongoHQ and MongoLab offer MongoDB hosting. MongoHQ has free (512 MB) and paid offers in the Eastern American data center. MongoLab is free (500 MB and co-payable offers in data centers in the USA and USA).
  • Windows Azure virtual machines are now in production, making it easy to deploy individual standalone or replicated installations in any data center (as well as configure access control lists to protect endpoints).

EDIT 7/15/2013 MongoLab now has an 8 GB replica set. I wrote about this here , which also has a link to the MongoLab post .

+3
source

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

More articles:


All Articles