ASP.NET Core与Azure构建现代Web应用：优势与实践

需积分: 0 99 浏览量更新于2024-07-18 收藏 3.46MB PDF 举报

"《现代Web应用架构设计：基于ASP.NET Core与Azure (.NET Core 2.1)》是一本由DevDiv、.NET和Visual Studio产品团队联合出品的书籍，它详细探讨了在当今开发环境中如何利用ASP.NET Core 2.1和Azure技术构建高效、现代化的Web应用程序。相较于传统的.NET开发，.NET Core和ASP.NET Core提供了诸多优势，包括轻量级架构、跨平台支持、容器化部署（如Docker）以及更好的性能和可扩展性。书中强调，如果你的应用程序对以下方面有较高要求，那么应考虑采用.NET Core作为服务器端开发平台： 1. 轻量级和高性能：.NET Core通过缩小基础库的大小和优化运行时环境，减少了启动时间和内存占用，从而提高应用程序的响应速度和效率。 2. 跨平台兼容：该版本的.NET Core实现了与Windows、Linux和macOS等多平台的无缝集成，使得开发者能够更方便地在不同操作系统上进行部署。 3. 容器化部署：书中提到了Docker的使用，它有助于实现应用程序的容器化部署，这不仅简化了部署流程，还提高了部署的一致性和可靠性，尤其是在微服务架构中。 4. 微服务架构的支持：通过介绍如何将应用程序拆分为小型、独立的服务，作者展示了如何利用ASP.NET Core和Azure来构建可扩展和灵活的系统架构。 5. 云原生集成：书中深入讲解了如何利用Azure提供的云服务，如Azure Functions、Azure App Service等，无缝集成到Web应用中，实现高效的云部署和管理。 6. 安全性与可维护性：.NET Core提供了强大的安全特性，以及现代化的开发工具链，有利于构建易于维护和更新的Web应用。 7. 社区和生态系统：作者还提及了来自社区的贡献者和Microsoft .NET团队的支持，这确保了技术的持续更新和最佳实践的共享。该书适合于.NET开发人员升级技能，特别是那些希望利用最新技术构建高质量Web应用的开发者。书中不仅提供理论知识，还有实用的示例和实战指导，适合希望通过学习提升实际项目能力的读者。由于版权原因，所有内容未经许可不得复制或传播。" 《Modern Web Applications with ASP.NET Core and Azure (dotNet2.1)》是一本权威且实用的指南，为开发人员揭示了如何在最新的技术和平台上构建和管理现代Web应用，是每个致力于技术进阶和项目实践者的宝贵资源。

10 Chapter 3

Choosing Between Traditional Web Apps and SPAs

Figure 3-3. The Angular SPA in the browser.

When to choose traditional web apps

The following is a more detailed explanation for picking traditional web applications.

Your application has simple, possibly read-only, client-side requirements

Many web applications are primarily consumed in a read-only fashion by the vast majority of their

users. Read-only (or read-mostly) applications tend to be much simpler than those that maintain and

manipulate a great deal of state. For example, a search engine might consist of a single entrypoint

with a textbox and a second page for displaying search results. Anonymous users can easily make

requests, and there is little need for client-side logic. Likewise, a blog or content management

system’s public-facing application usually consists mainly of content with little client-side behavior.

Such applications are easily built as traditional server-based web applications which perform logic on

the web server and render HTML to be displayed in the browser. The fact that each unique page of

the site has its own URL that can be bookmarked and indexed by search engines (by default, without

having to add this as a separate feature of the application) is also a clear benefit in such scenarios.

Your application needs to function in browsers without JavaScript support

11 Chapter 3

Choosing Between Traditional Web Apps and SPAs

Web applications that need to function in browsers with limited or no JavaScript support should be

written using traditional web app workflows (or at least be able to fall back to such behavior). SPAs

require client-side JavaScript to function; if it’s not available, SPAs are not a good choice.

Your team is unfamiliar with JavaScript or TypeScript development techniques

If your team is unfamiliar with JavaScript or TypeScript but is familiar with server-side web application

development, then they will probably be able to deliver a traditional web app more quickly than a

SPA. Unless learning to program SPAs is a goal, or the user experience afforded by a SPA is required,

traditional web apps are a more productive choice for teams who are already familiar with building

them.

When to choose SPAs

The following is a more detailed explanation of when to choose a Single Page Applications style of

development for your web app.

Your application must expose a rich user interface with many features

SPAs can support rich client-side functionality that doesn’t require reloading the page as users take

actions or navigate between areas of the app. SPAs can load more quickly, fetching data in the

background, and individual user actions are more responsive since full page reloads are rare. SPAs can

support incremental updates, saving partially completed forms or documents without the user having

to click a button to submit a form. SPAs can support rich client-side behaviors, such as drag-and-drop,

much more readily than traditional applications. SPAs can be designed to run in a disconnected mode,

making updates to a client-side model that are eventually synchronized back to the server once a

connection is re-established. You should choose a SPA style application if your app’s requirements

include rich functionality that goes beyond what typical HTML forms offer.

Note that frequently SPAs need to implement features that are built-in to traditional web apps, such

as displaying a meaningful URL in the address bar reflecting the current operation (and allowing users

to bookmark or deep link to this URL to return to it). SPAs also should allow users to use the browser’s

back and forward buttons with results that won’t surprise them.

Your team is familiar with JavaScript and/or TypeScript development

Writing SPAs requires familiarity with JavaScript and/or TypeScript and client-side programming

techniques and libraries. Your team should be competent in writing modern JavaScript using a SPA

framework like Angular.

References – SPA Frameworks

Angular

https://angular.io/

Comparison of 4 Popular JavaScript Frameworks

https://www.developereconomics.com/feature-comparison-of-4-popular-js-mv-frameworks

Your application must already expose an API for other (internal or public) clients

剩余114页未读，继续阅读

apolloflyhigh

粉丝: 0
资源: 6

ASP.NET Core与Azure构建现代Web应用：优势与实践

Architecting Modern Web applications with Asp.net core and Azure

Architecting-Modern-Web-Applications-with-ASP.NET-Core-and-Azure

Architecting Modern Web Applications

构建现代Web应用：ASP.NET Core与Azure云服务

构建现代Web应用：ASP.NET Core与Azure实战

Microsoft ASP.NET and AJAX Architecting Web Applications

Microsoft ASP.NET and AJAX: Architecting Web Applications

Microsoft.Press.Microsoft.ASP.NET.and.AJAX.Architecting.Web.Applications.Apr.2009.rar

Architecting .NET Web Applications for Scale & Performance (A Practical Guide)

Architecting Modern Java EE Applications epub

最新资源