差异发展的同时使用Windows Azure的 [英] Difference in development while using windows azure

问题描述

我的问题有两个部分，我知道他们是最基本的，但不能清除的想法让这个发布

我们正在筹建在Windows Azure上一个新的应用程序。阅读一些关于云的文章后，我必须建立一个像CRUD执行基本操作云示例应用程序。

1. 所以我想知道，是什么都根本的区别，你都觉得在Azure上的应用程序工作时。我已经建立了使用MVC框架为应用。我没有感觉到太大的差别在使用MVC和使用MVC云的应用程序在正常的Web应用程序写作code条款。
   什么是待办事项，同时建立一个云应用？




2. 我们正计划聘请一些人，有经验的手在使用Windows Azure的工作，也有在市场上的几个猎头轰击你resume.Though人成堆尚未在Windows Azure的工作他们有包括刚刚在那里简历。如何评价一个候选人来判断他对云计算的潜力。这个任何提示将是有益的。

解决方案

1。根本区别

Windows Azure的是要做工精细用ASP.NET。考虑到虚拟机在Windows Server 2008 R2 / SP2，有没有什么你不能这样做。导通premises应用程序和Windows Azure的应用程序之间的巨大差异是关于这些虚拟机的行为，Windows Azure中如何管理SLA和可用性，如何底层的客户机和主机操作系统的维护工作结束，依此类推。浮现在脑海中有几件事情：

• 负载均衡。有没有办法指挥交通到一个特定的VM实例，一组Web或工作者角色实例内（除非你建立自己的请求路由器）。所以，你需要计划无国籍


• 会话管理。有关第一点。不能使用进程内，需要缓存，表存储，或SQL供应商，这给无缝会话体验工作。


• 服务。 Windows Azure中提供身份管理，缓存，流量管理器（跨数据中心的负载均衡），CDN（对于斑点边缘缓存），Blob存储，表存储（无结构的NoSQL），等等。你必须在这些服务仔细看看，看看他们如何最好地满足您的应用程序。例如：表的存储扩展到100TB每个帐户，并具有非常低的每GB成本，但你的程序员需要学习的内容持久性的新方法，尤其是当他们已经​​习惯到SQL Server


• 部署。你需要了解如何维护您的应用程序，监视它，它的规模，升级。


• 可用性。你需要了解的Windows Azure如何管理你的操作系统（除非您使用的是你管理虚拟机），故障如何处理（例如硬件故障）


• 安全。 Windows Azure的SQL数据库的安全性是从SQL Server安全性的不同。

2。面试

建筑技能是至关重要的。编程技巧可以更容易地学习，特别是与 Windows Azure的培训工具包或一些好书。这里的东西我会查询，面试一个Windows Azure项目的候选人时，只是一个快速列表。一位经验丰富的Windows Azure的开发人员将能够处理这些的多数。

• 描述的场景，他们将结合（或单独）任务到同一个（或单独）的角色


• 解释如何监控和扩展应用程序


• 了解升级的应用程序的各个方面


• 了解如何安装和运行第三方工具和替代（non-.NET）语言


• 设计师对成本和性能之间VS可用性


• 了解存储解决方案（SQL，第三方SQL和放大器; NoSQL的，斑点/表/队列）


• 了解Windows Azure的队列与服务总线队列的利弊


• SQL Server和Windows Azure的SQL数据库，包括联合会，安全性，瞬时性故障，跨数据库的查询和交易之间的差异


• 了解内容分发网络边缘的高速缓存的性能（和限制）

My question has two parts I know they are basic ones but not able to clear the thoughts so posting this.

We are planning to build a new app on windows azure. after reading some of the articles on cloud I have build a sample application on cloud that perform basic operation like CRUD.

1. So I want to know that what are all fundamental difference you all felt while working on azure app. I have built the application using MVC as framework. I have not felt much of difference in terms of writing code in normal web app using MVC and a cloud app using MVC. What are the to-dos while building an cloud app?.

2. We are planning to hire some people that have hands on experience in working with Windows azure, there are several head hunters in the market that bombard you with piles of resume.Though people have not worked on windows azure they have just included in there resume. How to evaluate a candidate to judge his potential on cloud computing . Any tips for this would be helpful.

解决方案

1. Fundamental differences

Windows Azure is going to work fine with ASP.NET. Considering the VMs are Windows Server 2008 R2/SP2, there's not much you can't do. The big differences between on-premises apps and Windows Azure apps are about how these VMs behave, how Windows Azure manages SLA and availability, how underlying guest and host OS maintenance is done, and so on. A few things that come to mind:

• Load balancing. There's no way to direct traffic to a specific VM instance within a set of Web or Worker role instances (unless you build your own request router). So you need to plan for statelessness
• Session management. Related to first point. Can't use inproc, need to work with Cache, table storage, or SQL providers, which give seamless session experience.
• Services. Windows Azure provides identity management, cache, traffic manager (load balancing across data centers), CDN (edge cache for blobs), blob storage, table storage (schemaless, NoSQL), and more. You need to look at these services carefully and see how they best fit your app. For instance: Table storage scales to 100TB per account and has a very low per-GB cost, yet your programmers will need to learn a new way of content persistence, especially if they're used to SQL Server.
• Deployment. You'll need to understand how to maintain your app, monitor it, scale it, upgrade it.
• Availability. You'll need to understand How Windows Azure manages your OSs (unless you're using Virtual Machines that you manage), how failures are dealt with (e.g. hardware failure)
• Security. Windows Azure SQL Database security is different from SQL Server security.

2. Interviewing

Architecture skills are critical. Programming skills can be learned more easily, especially with the Windows Azure Training Kit or some good books. Here's just a quick list of things I'd be inquiring about, when interviewing candidates for a Windows Azure project. A seasoned Windows Azure developer would be able to handle the majority of these.

• Describe scenarios where they would combine (or separate) tasks into the same (or separate) roles
• Explain how to monitor and scale an app
• Understand the various aspects of upgrading an app
• Know how to install and run 3rd-party tools and alternative (non-.NET) languages
• Architect for cost vs performance vs availability
• Know about storage solutions (SQL, 3rd-party SQL & NoSQL, blobs/tables/queues)
• Know the pros and cons of Windows Azure Queues vs. Service Bus queues
• Differences between SQL Server and Windows Azure SQL Database, including federations, security, transient faults, cross-database queries and transactions
• Understand the capabilities (and limitations) of Content Delivery Network edge-cache

这篇关于差异发展的同时使用Windows Azure的的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！