您可以非常轻松地在 Windows Azure 中运行 mongodb.我在 MongoSV 上展示了这个 - 视频这里.

You can very easily run mongodb in Windows Azure. I presented this at MongoSV - video here.

编辑:2011 年 12 月，10gen 在 github.这包含一个副本集项目，以及一个使用副本集存储的演示 ASP.NET MVC 应用程序(取自 Windows Azure 平台培训工具包).

EDIT: In December 2011, 10gen published their official MongoDB+Azure code on github. This contains a project for replica-sets, as well as a demo ASP.NET MVC application (taken from the Windows Azure Platform Training Kit) that uses a replica set for its storage.

独立服务器很简单，除了您必须处理横向扩展:您不能同时拥有独立服务器的多个实例，因此您需要为此做好计划:从负载平衡器中取出除一个之外的所有实例, 或者只有在可以获得云驱动锁的情况下才启动 mongod.

Standalone servers are straightforward, except you have to deal with scale-out: you can't have multiple instances of a standalone server simultaneously, so you'll need to plan for this: take all but one out of the load balancer, or only launch mongod if you can acquire the Cloud Drive lock.

副本集是可行的，正如我在 MongoSV 上演示的那样.但是，我没有介绍正常关闭副本集以确保零数据丢失的复杂性.

Replicasets are doable, as I demonstrated at MongoSV. However, I didn't cover the intricacies of graceful shutdown of a replicaset to ensure zero data loss.

您也可以运行 memcached - 请参阅 David Aiken 的 帖子 关于这个.注意:现在 AppFabric Cache 服务已上线，您应该研究使用它而不是 memcached 的利弊.在成本方面，AppFabric Cache 的运行次数应该少得多，因为您无需为托管缓存的角色实例付费.有关 AppFabric 缓存的更多信息 这里.

You can run memcached as well - see David Aiken's post about this. Note: Now that the AppFabric Cache service is live, you should look into the pros/cons of using that over memcached. Cost-wise, AppFabric Cache should run much less, as you don't have to pay for role instances to host your cache. More info about AppFabric Cache here.