ASP.NET Core与SignalR：构建实时应用实战指南

需积分: 13 122 浏览量更新于2024-07-19 2 收藏 26.53MB PDF 举报

"Apress的《实时Web应用开发：使用ASP.NET Core、SignalR、Docker和Azure》是由Rami Vemula撰写的一本专业书籍，专为希望通过Microsoft技术实现端到端应用程序开发的开发者和软件工程师设计。本书旨在指导读者设计、开发并部署一个实际的跨平台Web应用，利用现代开源技术如ASP.NET Core、SignalR进行实时通信，以及通过Docker进行容器化和Azure的持续部署。在学习过程中，读者将掌握的核心知识点包括： 1. 设计现代Web应用架构，采用Materialize CSS风格进行用户界面设计。 2. 使用.NET Core理解新时代的开发环境，掌握其核心组件和技术。 3. 学习Material Design的实践，创建吸引人的主题。 4. 了解Azure存储服务，包括数据管理和操作。 5. 掌握xUnit.net进行测试驱动开发，确保代码质量。 6. 安全方面，通过ASP.NET Core Identity和OAuth 2.0协议实现应用安全。 7. 使用Azure Table Storage进行主数据管理，确保数据一致性。 8. 学习如何有效处理日志和异常，提高应用的健壮性。 9. 视图组件的使用，增强导航功能和用户体验。 10. 熟悉表单和验证，确保用户输入的有效性。 11. 通过SignalR实现服务器与客户端的实时通信，提升交互性能。 12. 掌握GitHub平台用于代码版本控制，以及Travis CI的集成，实现持续集成。 13. 准备生产环境，创建Docker镜像，简化部署过程。 14. 将应用部署到Azure Linux虚拟机，利用Docker Cloud实现自动化部署。本书适合那些希望深入学习和实践使用ASP.NET Core、SignalR和Azure构建实时Web应用的开发人员，丰富的代码示例可用于现有项目的升级或扩展。通过阅读这本书，读者将获得开发高效、安全且可扩展的现代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页未读，继续阅读

DoomLord

粉丝: 114
资源: 1318

ASP.NET Core与SignalR：构建实时应用实战指南

[Packt Publishing] ASP.NET MVC 4 Mobile App Development

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

SignalR – Real-time Application Development, 2nd (pdf英文原版第二版)

关于springboot的英文文献

springboot的参考文献

springboot框架外文参考文献列表

帮我找一下可以写再javaweb毕设里的英文参考文献

spring boot项目英文文献

列举几个SpringBoot相关的技术文献,以文献引用的格式展示

springboot外文文献

最新资源