企业级Web开发实践指南

需积分: 10 165 浏览量更新于2024-07-22 收藏 44.07MB PDF 举报

"Enterprise Web Development" 在企业级Web开发领域，本书由Yakov Fain、Victor Rasputnis、Anatole Tartakovsky和Viktor Gamov四位专家共同撰写，涵盖了企业级Web应用开发的各个方面。这本书旨在提供一套全面的指南，帮助开发者理解和掌握构建高效、可扩展且具有高度可靠性的企业级Web应用程序的关键技术和实践。书中可能涵盖了以下几个核心知识点： 1. **Web框架**：讨论了各种用于企业级开发的Web框架，如Spring、JavaServer Faces (JSF)、AngularJS等，这些框架能够简化开发过程，提高代码复用性和可维护性。 2. **后端架构**：深入探讨了如何设计和实现高效的后端架构，包括数据库设计、服务化（Service-oriented Architecture, SOA）、微服务架构以及分布式系统的设计原则。 3. **前端技术**：详述了现代前端开发技术，如HTML5、CSS3、JavaScript，以及响应式设计和移动优先策略，确保应用程序在各种设备上都能提供良好的用户体验。 4. **数据管理**：讨论了关系型与非关系型数据库的使用场景，如MySQL、Oracle、MongoDB等，并涉及ORM（对象关系映射）工具，如Hibernate和JPA。 5. **安全性**：涵盖Web应用的安全实践，包括认证、授权、加密、防止SQL注入和XSS攻击等，确保企业级应用的数据安全。 6. **性能优化**：讲解如何通过缓存策略、负载均衡、CDN（内容分发网络）和性能监控来优化Web应用的性能。 7. **持续集成与自动化测试**：介绍Jenkins、Git等工具在持续集成中的应用，以及JUnit、Selenium等自动化测试框架，以确保软件质量。 8. **云计算与DevOps**：讨论如何利用AWS、Azure、Google Cloud等云平台部署和管理企业级Web应用，以及DevOps文化、CI/CD流程的实施。 9. **敏捷开发与项目管理**：介绍了Scrum、Kanban等敏捷开发方法，以及如何使用JIRA、Trello等工具进行项目管理和团队协作。 10. **最佳实践与案例研究**：书中可能会包含真实的企业级项目案例，分析它们的成功经验和教训，为读者提供实际操作的参考。这本书的出版日期为2014年6月，可能已经涵盖了当时最新的技术趋势和最佳实践。尽管随着时间的推移，技术会有所更新，但书中的核心理念和基本原则对于任何希望从事企业级Web开发的人员来说仍然具有很高的价值。

Introducing the Save The Child Application

To make this book more practical, we decided not to give you unrelated code snippets

illustrating various syntax or techniques, but to bring all of that together in a working

application (just the UI portion). While learning the various frameworks, libraries, and

approaches to building UIs for web applications, you’ll be writing multiple versions of

the same web application—Save The Child (see Figure P-1). It’s a sample charity appli‐

cation used to collect donations for children who need medical attention.

Figure P-1. Save The Child—a sample application

This web application will allow people to register, donate, find local kids who need help,

match donors and recipients, upload images and videos, and display statistics.

Is This Even an Enterprise App?

While looking at the preceding image, you might be thinking, “This doesn’t look like

an enterprise application.” Let’s see. Do you believe that an enterprise application has to

consist of boring gray windows with lots of grids and forms, and some charts? True, but

we have all of these elements in our application, too:

• Clicking the Donate Now button reveals a form that has to be filled out and sent to

a payment processing system.

xiv | Preface

• The interactive live pie chart is something that many modern enterprise dashboards

include.

• Clicking the Table tab (right next to the Chart tab) shows the same donation stats

in a grid (that one is grayish).

• Integration with the mapping API allows you to visually present the locations of

important events for this business or nonprofit organization.

• Under the hood, this pretty window will use the high-speed, full-duplex commu‐

nication protocol WebSocket.

As a matter of fact, the company that employs the authors of this book has a customer

that is a nonprofit organization that is in the business of helping people fighting a certain

disease. That application has two parts: consumer-facing and back-office. The former

looks more colorful, whereas the latter has more gray grids indeed. Both parts process

the same data, and this organization can’t operate if you remove either of these parts.

Would these features make Save The Child an enterprise web application? Yes, because

it can help our imaginary nonprofit organization run its business: collecting donations

for sick kids. Would you rather see a fully functioning Wall Street trading system? Maybe.

But this book and our sample application incorporate all software components that

you’d need to use for developing a financial application.

How We Are Going to Build This App

Instead of presenting unrelated code samples, we decided to develop multiple versions

of the same web application, built with different libraries, frameworks, and techniques.

This approach allows you to compare apples to apples and to make an educated decision

about which approach best fits your needs.

First, we’ll show how to build this application in pure HTML/JavaScript. Then, we’ll

rewrite it using the jQuery library, and then with the Ext JS framework. Users will be

able to see where different charity events are being run (via Google Maps integration).

The page will integrate a video player and display a chart with stats on donors by geo‐

graphical location. One of the versions shows how to modularize the application; this

is a must for any enterprise system. Another version shows how to use WebSocket

technology to illustrate the server-side data push while adding an auction to this web

application. The final chapters of the book show various ways of building different

versions of the same Save The Child application to run on mobile devices (responsive

design, jQuery Mobile, Sencha Touch, and PhoneGap). We believe that this application

will help you to compare all these approaches and select those that fit your objectives.

Preface | xv

Although you can write your programs in any text editor, using specialized integrated

development environments (IDEs) is more productive, and we’ll use the Aptana Studio

IDE by Appcelerator and the WebStorm IDE by JetBrains.

How the Book Is Organized

Even though you may decide not to read some of the chapters, we still recommend that

you to skim through them. If you’re not familiar with JavaScript, start from the online

bonus chapter.

Chapters 1 and 2 are must reads; if you can’t read JavaScript code or are not familiar

with CSS, Ajax, or JSON, the rest of the book will be difficult to understand. On the

other hand, if you’re not planning to use, say, the Ext JS framework, you can just skim

through Chapter 4. Following is a brief book outline.

The Preface includes a brief discussion of the difference between enterprise web appli‐

cations and websites. It also touches on the evolution of HTML.

Chapter 1 describes the process of mocking up the application Save The Child, which

will solicit donations to children, embed a video player, integrate with Google Maps,

and eventually feature an online auction. We show you how to gradually build all the

functionality of this web application while explaining each step of the way. By the end

of this chapter, we’ll have the web design and the first prototype of the Save The Child

application written using just HTML, JavaScript, and CSS.

Chapter 2 is about bringing external data to web browsers by making asynchronous

calls to a server. The code from the previous chapter uses only hardcoded data. Now it’s

time to learn how to make asynchronous server calls by using Ajax techniques and

consume the data in JSON format. The Save The Child application will start requesting

the data from the external sources and sending them the JSON-formatted data.

Chapter 3 shows how to use a popular jQuery library to lower the amount of manual

coding in the Save The Child application. First, we introduce the jQuery Core library,

and then rebuild our Save The Child application with it. In the real world, developers

often increase their productivity by using JavaScript libraries and frameworks.

Chapter 4 is a mini tutorial of a comprehensive JavaScript framework called Ext JS. This

is one of the most feature-complete frameworks available on the market. Sencha, the

company behind Ext JS, has managed to extend JavaScript to make its syntax closer to

classical object-oriented languages. Sencha also developed an extensive library of the

UI components. Expect to see another rewrite of the Save The Child application here.

Chapter 5 is a review of productivity tools (including npm, Grunt, Bower,Yeoman, and

CDB) used by enterprise developers. It’s about using build tools, working with code

generators, and managing dependencies (a typical enterprise application uses various

software that needs to work in harmony).

Preface | xvii

Chapter 6 explains how to modularize large applications. Reducing startup latency and

implementing lazy loading of certain parts of the application are the main reasons for

modularization. We give you an example of how to build modularized web applications

that won’t bring large, monolithic code to the client’s machine, but rather loads the code

on an as-needed basis. You’ll also see how to organize the data exchange between pro‐

gramming modules in a loosely coupled fashion. The Save The Child application is

rewritten with the RequireJS framework, which will load modules on demand rather

than the entire application.

Chapter 7 is dedicated to test-driven development with JavaScript. To shorten the de‐

velopment cycle of your web application, you need to start testing it in the early stages

of the project. It seems obvious, but many enterprise IT organizations haven’t adopted

agile testing methodologies, which costs them dearly. JavaScript is dynamically typed

interpreted language—there is no compiler to help identify errors as it’s done in com‐

piled languages like Java. This means that a lot more time should be allocated for testing

JavaScript web applications. We cover the basics of testing and introduce you to some

of the popular testing frameworks for JavaScript applications. Finally, you’ll see how to

test the Save The Child application with the Jasmine framework.

Chapter 8 shows how to substantially speed up interactions between the client and the

server by using the WebSocket protocol introduced in HTML5. HTTP adds a lot of

overhead for every request and response object that serve as wrappers for the data. You’ll

see how to introduce a WebSocket-based online auction to the new version of our Save

The Child application. This is what Ian Hickson, the HTML5 spec editor from Google,

said about why the WebSocket protocol is important:

Reducing kilobytes of data to 2 bytes is more than a little more byte efficient, and reducing

latency from 150 ms (TCP round-trip to set up the connection plus a packet for the message)

to 50 ms (just the packet for the message) is far more than marginal. In fact, these two

factors alone are enough to make WebSocket seriously interesting to Google.

Chapter 9 is a brief introduction to web application security. You’ll learn about vulner‐

abilities of web applications and will get references to recommendations on how to

protect your application from attackers. This chapter concludes with some of the

application-specific security considerations (like regulatory compliance) that your busi‐

ness customers can’t ignore.

Chapter 10 opens up a discussion of how to approach creating web applications that

should run not only on desktops, but also on mobile devices. In this chapter, you become

familiar with the principles of responsive design, which allow you to have a single code

base that will be flexible enough to render a UI that looks good on large and small

screens. You’ll see the power of CSS media queries that automatically reallocate UI

components based on screen width of the device on which the website is being viewed.

The new version of the Save The Child application will demonstrate how to go about

responsive design.

xviii | Preface

剩余636页未读，继续阅读

yaorui2568

粉丝: 5
资源: 5

企业级Web开发实践指南

Drupal 8: Enterprise Web Development

EnterpriseWebBook_sources:本书“ Enterprise Web Development”中的代码示例-web development source code

ASP.NET Core Cloud-ready Enterprise Web Application Development epub

ASP.NET Core Cloud-ready Enterprise Web Application Development azw3

ASP.NET Core: Cloud-ready, Enterprise Web Application Development

ASP.NET Core_ Cloud-ready, Enterprise Web Application Development

HTML5 Enterprise Application Development

Guide to Enterprise PHP Development

WebLogic Web Development

Packt - Ruby on Rails Enterprise Application Development (Oct 2007)

最新资源