运行Azure的模拟器本地生产 [英] Running Azure emulators locally for production

问题描述

我有一个项目（实际数），我最终想将其部署到Azure的，所以我的VS解决方案包含Web和辅助角色，并在我的本地模拟器运行成功。 （我也用表和BLOB存储）。

我有一个Windows 2012服务器暴露在WWW端口80，想探探不使用Azure的帐户或在该花钱（还）。

当我部署我的W2012服务器上的Azure的仿真器和基本运行Azure的本地，可以在这个即使在生产环境中进行（很轻的流量）？性能会受到严重影响？旨在模拟器将在所有像使用或他们大大下降，在性能上有利于记录和调试的？

我当然知道，这是不建议作为一个整体。仿真器是不用于生产和所有。我明白那个。不过我很好奇，如果有人试图东西simular。

更新：我想我是不是我​​的问题不够具体。我不好，对不起。因此，更具体：

1. 在什么样的方式是由不履行背负的模拟器聚焦，记录和调试？




2. 是模拟器稳定吗？有没有人有他们崩溃或减慢经验？



3. 请模拟器始终，在任何情况下，返回相同的结果作为Azure的云版本？

解决方案

有根本性的差异计算和计算模拟器之间的，还有的差异存储和存储之间的模拟器的。虽然我提供的链接可能有点过时（我找不到更近的），也有一些直接的事情，你应该看到：

计算

• 负载均衡器的行为有所不同（例如：您仍可以访问取出旋转的情况下）


• 在过程中充分VS虚拟机运行的实例（这意味着你不能测试安装软件的启动脚本，无需先卸载软件在本地）


• 没有任何SLA


• 您的环境只是作为你的本地计算机的安全


• IP地址管理是不同的


• 对于虚拟网络不支持（你将无法使用虚拟机进行互操作，例如，通过内部端口）

存储

• 无缩放（Azure存储是一个巨大的多tentant系统，扩展容易地请求流量上升）


• 无耐久性（Azure存储是三重复制和可选的地理复制;本地存储坐落在一个SQL数据库）


• 斑点被限制为2GB（VS在Azure存储200GB / 1TB）
  
  
  
  • 跨表和队列存储其他一些差异）
  
  

另外：你有你的模拟部署（无PowerShell中，没有CLI）没有命令行控制，你将无法查看通过门户网站/任何设置

有是的服务，您可以在Windows Server，如服务总线和缓存上本地运行的，你甚至可以安装的天青软件包适用于Windows Server。

底线：你不能在Azure中的模拟器中运行;您code是本地进程与当地独立的数据库进程中执行。您将有0 SLA，非冗余存储，绝对没有可视性系统的整体状况。这根本就不是一个生产环境。

I have a project (actually several) that I eventually like to deploy to Azure, so my VS solution contains both web and worker roles and is running successfully on my local emulators. (I also use Table and Blob storage).

I have a Windows 2012 server with port 80 exposed to the www and would like to test the waters without using an Azure account or spending money on that (yet).

When I deploy the Azure emulators on my W2012 server and basically run Azure locally, can this even be done in a production-like environment (with very light traffic)? would performance be impacted seriously by that? Are the emulators intended to be used like that at all or do they decline much in performance in favor of logging and debugging?

I am of course aware that this is not recommended as a whole. Emulators are not for production and all that. I understand that. But I am very curious if someone tried something simular.

Update: I think I was not specific enough with my question. My bad, sorry. So more concrete:

1. In what way is are the emulators burdened by non-performance focused, like logging and debugging?

2. Are the emulators stable? Does anyone have experience with them crashing or slowing down?

3. Do the emulators always, under any circumstance, return the same result as the cloud version of Azure?

解决方案

There are fundamental differences between Compute and Compute emulator, as well as differences between Storage and Storage emulator. While the links I provided may be a bit outdated (I can't find more recent ones), there are a few immediate things that you should see:

Compute:

• Load balancer behaves differently (for instance: you can still access instances taken out of rotation)
• Instances run in processes vs full virtual machines (meaning you can't test startup scripts that install software, without first uninstalling software locally)
• No SLA whatsoever
• Your environment is only as secure as your local computer
• IP address management is different
• No support for virtual networks (you won't be able to interoperate with Virtual Machines, for example, via internal ports)

Storage:

• No scaling (Azure Storage is a massive multi-tentant system, scaling easily as request traffic rises)
• No durability (Azure Storage is triple-replicated and optionally geo-replicated; local storage sits in a SQL database)
• Blobs are limited to 2GB (vs 200GB / 1TB in Azure Storage)
  • Several other differences across Table and Queue storage)

Also: You'll have no command-line control of your emulated deployment (no PowerShell, no CLI), and you won't be able to view/set anything via the portal.

There are services you can run locally on Windows Server, such as Service Bus and Cache, and you can even install the Azure Pack for Windows Server.

Bottom line: You're not running in Azure with the emulator; your code is executed in local processes with a local standalone database process. You'll have 0 SLA, non-redundant storage, absolutely no visibility into overall system health... It's simply not a production environment.

这篇关于运行Azure的模拟器本地生产的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！