Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are fundamental <a href="http://msdn.microsoft.com/en-us/library/windowsazure/gg432960.aspx" rel="noreferrer">differences</a> between Compute and Compute emulator, as well as <a href="http://msdn.microsoft.com/en-us/library/windowsazure/gg433135.aspx#" rel="noreferrer">differences</a> 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:</p> <p><strong>Compute</strong>:</p> <ul> <li>Load balancer behaves differently (for instance: you can still access instances taken out of rotation)</li> <li>Instances run in processes vs full virtual machines (meaning you can't test startup scripts that install software, without first uninstalling software locally)</li> <li>No SLA whatsoever</li> <li>Your environment is only as secure as your local computer</li> <li>IP address management is different</li> <li>No support for virtual networks (you won't be able to interoperate with Virtual Machines, for example, via internal ports)</li> </ul> <p><strong>Storage</strong>:</p> <ul> <li>No scaling (Azure Storage is a massive multi-tentant system, scaling easily as request traffic rises)</li> <li>No durability (Azure Storage is triple-replicated and optionally geo-replicated; local storage sits in a SQL database)</li> <li>Blobs are limited to 2GB (vs 200GB / 1TB in Azure Storage) <ul> <li>Several other differences across Table and Queue storage)</li> </ul></li> </ul> <p>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.</p> <p>There <em>are</em> services you can run locally on Windows Server, such as Service Bus and Cache, and you can even install the <a href="http://technet.microsoft.com/en-us/library/dn296435.aspx" rel="noreferrer">Azure Pack</a> for Windows Server.</p> <p>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.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload