使用ASP.NET Core, SignalR, Docker和Azure构建实时Web应用

需积分: 10 19 浏览量更新于2024-07-17 收藏 26.56MB PDF 举报

"Real-Time Web Application Development.2017" 本书主要关注的是实时Web应用程序开发，作者Rami Vemula在2017年出版的这本书中详细介绍了如何使用ASP.NET Core、SignalR、Docker和Azure来构建实时交互的Web应用。以下是关于这些技术的详细知识点： 1. **ASP.NET Core**： ASP.NET Core是微软推出的跨平台、开源的Web框架，用于构建高性能、模块化和可移植的Web应用。它支持.NET Framework和.NET Core运行时。ASP.NET Core引入了Kestrel服务器，提供了一个轻量级且高效的HTTP服务器，可以部署在Windows、Linux和macOS上。此外，ASP.NET Core中的MVC（Model-View-Controller）和API设计模式让开发者能够更灵活地构建Web应用。 2. **SignalR**： SignalR是ASP.NET中用于实现实时双向通信的库。它简化了服务器到客户端的推送更新，使得Web应用能够像桌面或移动应用一样实时更新。SignalR支持多种传输方式，包括WebSocket、Server-Sent Events (SSE)、Forever Frame 和 Long Polling，以适应不同浏览器和服务器环境。通过Hub接口，开发者可以轻松地向客户端广播消息或调用客户端方法。 3. **Docker**： Docker是一种流行的容器化技术，允许开发者将应用及其依赖打包到一个可移植的容器中，从而实现一致的运行环境。在实时Web应用开发中，Docker可以帮助快速部署和扩展应用，确保每个实例都具有相同的基础环境。Docker Compose可以用来定义和运行多容器的应用，简化了服务的配置和管理。 4. **Azure**： Microsoft Azure是一个全球化的云服务平台，提供多种服务，如计算、存储、数据库、网络和分析。在实时Web应用的上下文中，Azure可以提供如Azure SignalR Service，它是一个托管服务，专门针对SignalR进行了优化，可以自动处理连接管理和负载均衡。此外，Azure App Service可以用来托管ASP.NET Core应用，提供高可用性和弹性伸缩。Azure Kubernetes Service (AKS) 可以帮助管理和部署Docker容器，实现自动化缩放和故障恢复。 5. **开发实践**：书中可能会涵盖如何集成这些技术，包括设置开发环境，创建实时Web应用，使用SignalR进行实时通信，利用Docker进行应用的封装和部署，以及如何在Azure上配置和管理服务。还会涉及调试、测试和监控实时应用的策略，以及安全性、身份验证和授权等方面。通过学习这些技术，开发者能够构建出能够即时响应用户操作、实时推送数据的Web应用，适用于聊天室、股票交易、在线游戏、协作工具等多种场景。

R. Vemula, Real-Time Web Application Development, https://doi.org/10.1007/978-1-4842-3270-5_1

CHAPTER 1

Designing a Modern Real-World

Web Application

In this modern era of the digital world, technology is no longer an auxiliary system but an integral part of the

entire social ecosystem. Our current-day sophisticated devices, along with cutting-edge technologies, have

made the entire world into a global village. People from different parts of the world, in spite of their diversity,

can collaborate and solve complex challenges. Over the past decade, the open source community has played

a pivotal role in evolving technology and setting the pace for innovation.

The ever-changing cadence of technology and tools has prompted a new generation of developers and

engineers to rely mostly on Internet resources to educate themselves and deliver solutions. Although that

approach still works in delivering solutions, it doesn’t help in providing a panoramic view of the software-

building process. Although different software development life cycle (SDLC) methodologies follow different

processes, the most important ones are detailing functional requirements, system design, implementation,

testing, deployment, and maintenance. Except for the testing part, this book will provide a holistic view of

the software development process using the latest open source technologies and tools.

In this chapter, you will learn the basic phases of the software development life cycle. We will simulate

a real-world business use case through a fictitious US company, Automobile Service Center. We will

brainstorm the typical day-to-day challenges faced by this company and propose prospective solutions

through a web application that we’ll build with the latest technologies throughout the rest of the book. We’ll

start by defining the technologies that we are going to use in building the application. Then we’ll design the

logical architecture followed by continuous integration and deployment pipeline of the application. Finally,

we will conclude the chapter by exploring the software prerequisites for our development environment.

■ Note My primary motive in writing this book is to introduce you to the experience of end-to-end software

application development using .NET Core, ASP.NET Core, SignalR, Docker, and Microsoft Azure. This book

provides a high-level overview of software development methodologies, and a detailed exploration is beyond

the scope of this book.

CHAPTER 1 ■ DESIGNING A MODERN REAL-WORLD WEB APPLICATION

Overview of Application Development Strategies and

Processes

The incredible pace of the current generation's digital innovation is not only transforming the creative

process, but also influencing the incubation period for the latest technologies. Because of so many technical

options being available to solve any given unique business challenge, technologists need to be more

careful than ever before in offering prospective solutions. The current marketplace requires any technical

professional to be adept at three major tasks: exploring, understanding, and adopting.

Let’s look at an example of creating a next-generation e-commerce application. To serve a large global

audience, this application should be highly scalable and deliver optimistic performance, be available on

various devices, support a rich and clean user experience, include real-time data analytics and reports,

be cost-effective and easy to maintain, and more. To deliver this e-commerce solution, we could turn to a

wide range of technical options. We could use the traditional ASP.NET MVC in combination with JQuery,

SQL Server, HDInsight, and Power BI. Other options include a LAMP stack with Hadoop Spark or a MEAN

stack with R-powered analytics. The list goes on. We must carefully evaluate all potential solutions and then

continue with the design and development process.

Many proven methodologies in the software industry can help us in the various phases of application

development. These methodologies can be considered as frameworks for planning and controlling the

process of developing software. Popular methodologies include the waterfall model, rapid application

development, agile software development, and the prototype model. Different software organizations and

projects use different methodologies based on their engineering and operational criteria. In fact, some

organizations use their own tailored hybrid development methodologies and processes. Regardless of which

software methodology we follow, we have to adhere to certain phases that are common to all methodologies.

We will follow these phases, depicted in Figure1-1, throughout this book as we journey through application

development.

Requirements

Gathering & Analysis

System DesignPlanning

Development Testing Deployment

Maintenance &

Operations

Figure 1-1. Phases of the software development life cycle

Requirements Gathering and Analysis

In this phase, we capture all the functional requirements of the software that we are planning to build.

We create a brief functional specification document and then share it with all stakeholders.

CHAPTER 1 ■ DESIGNING A MODERN REAL-WORLD WEB APPLICATION

Planning

During this phase, we start by augmenting staff and creating timelines for the project. Although it’s not

mandatory, we can organize all functionalities into logical groups and place them in different iterations, or sprints.

We document the proposed project plan along with critical timelines as part of this phase’s deliverables.

System Design

In this phase, we design the entire system’s architecture. We have to list all technologies, tools, and

commercial off-the-shelf (COTS) products that will be used during application development. The key

deliverables of this phase are the specifications for the logical and physical architecture.

Development

The actual coding and development of the software is done during this phase. This phase may follow its own

development strategies, such as test-driven development (TDD) or domain-driven development(DDD). In

TDD, we write unit tests before developing the application code; so at first, all the unit tests will fail, and then

we have to add or refactor application code to pass the unit tests. This is an iterative process that happens

every time a new functionality is added or an existing one is modified.

Testing

During this phase, we integrate all the components of the software (for example, a web application might

consume web API endpoints that are hosted differently, and these should be integrated as part of the testing

phase). Then we test the application. The testing process usually comprises system integration testing (SIT)

followed by user acceptance testing (UAT). Testing should be an iterative and ongoing activity that makes the

application more stable and robust.

Deployment

Deployment activity includes all the procedures required for hosting the application on staging and

production environments. Modern source-version-control systems support automated deployments to

configured environments. Having said that, manual monitoring (for example, DEV, SIT, UAT, STAG, and

PROD) should occur while promoting builds across various environments.

Maintenance and Operations

After the application is hosted and made available to the audience, unanticipated issues and errors (or even

code-level exceptions) may arise, for multiple reasons. Maintenance is the phase when we closely monitor

the hosted application for issues and then release hotfixes and patches to fix them. Operational tasks such as

software upgrades on servers and backups of databases are performed as part of the maintenance activity.

As this book walks you through the end-to-end development of a web application, it will touch on every

phase of application development except testing.

■ Note As mentioned previously, it is not my intention to proclaim that the cited methodologies are the

only widely accepted options. But the preceding application development phases are the most common and

frequently used practices for software projects.

CHAPTER 1 ■ DESIGNING A MODERN REAL-WORLD WEB APPLICATION

Introduction to the Automobile Service Center Application

In this book, we’ll take a near-real-world business requirement and deliver an end-to-end technical

solution. I believe that this type of demonstration will help you understand the concepts better because

of their practical implementations. The step-by-step process of building the web application will help you

remember the concepts you’ve learned in each chapter.

The Automobile Service Center is a fictitious US company that provides all types of car maintenance

services to its customers. This company has more than 20 branches across the West Coast and serves more

than 3,000 customers a day. It provides a personalized experience to its end customers in all areas related to

car repairs and maintenance.

The Automobile Service Center provides car maintenance services in the following areas: Engine and

Tires, Air Conditioning, Auto and Manual Transmissions, Electrical Systems, Batteries, Brakes, and Oil

Changes. This Service Center also takes care of specific customer requests and complaints about the cars.

At times it provides additional services including towing, pickup and drop, insurance, and financial-related

offerings. This Service Center employs more than 1,500 professionals in various capacities. Most employees

are service engineers who are responsible for the daily service operations, while other employees take care

of responsibilities such as ordering spare parts, managing logistics, and running financial operations.

Today the Automobile Service Center is facing a major business challenge: maintaining good customer

communication. The company lacks an affordable and reliable method of real-time communication with

customers (for example, live chats between customers and service engineers, or e-mail/text notifications

about service updates). A majority of customers want real-time service updates and automated service

appointments. Currently, the company requires its customers to walk in to a Service Center branch and

discuss the services with an available service engineer, who opens a service job card that documents the

details. During the service work, all the communications between the service engineer and the customer

occur through phone calls, and the points discussed are attached back to the job card. After the service is

done, the customer pays the invoice amount, and the service engineer closes the job card. The Automobile

Service Center has identified that this entire process is inefficient and is diminishing its brand value for the

following reasons:

• Causes service delays because of a high dependency on the human factor

• Lack of transparency

• Creates opportunities for miscommunication

• Provides no precision in effort and estimations

• Doesn’t enable the company to reach out to customers and promote great deals,

discounts, and packages

Throughout this book, we’ll help the Automobile Service Center overcome these challenges by creating

a modern web application designed with cutting-edge technologies. By end of this book, we’ll have a fully

functional, production-ready web application, as shown in Figure1-2.

剩余606页未读，继续阅读

brucejing2

粉丝: 0
资源: 21

使用ASP.NET Core, SignalR, Docker和Azure构建实时Web应用

Real-Time Web Application Development

Real-time Web Application Development using Vert.x 2.0

Real-time Web Application Development using Vert.x 2.0 英文 pdf版本

Real-time Web Application Development using Vert.x 2.0(PACKT,2013)

Socket.IO Real-time Web Application Development

Real-Time Web Application Development With ASP.NET Core, SignalR, Docker,

Real-Time Web Application Development With ASP.NET Core, SignalR, Docker, epub

[Packt Publishing] SignalR Real-time Application Development

PHP.7.Real.World.Application.Development

MEAN.Web.Development.2nd.Edition

最新资源