Develop best practices for Web 2.0 applications based on IBM Lotus Domino

Introduction: This article describes best practices for developing WEB 2.0 enterprise applications based on IBM Lotus Domino. These best practices cover the entire lifecycle of system development, including the system design phase, implementation phase, and system assembly and deployment phases. Based on the methods described in this article, you can efficiently develop high-quality Domino-based WEB 2.0 enterprise applications.

Background profiles and challenges

Domino is a flagship product under IBM Lotus, which provides a multi-level security solution, built-in integrated collaborative service applications and directory services, and provides a flexible database replication mechanism, which is an important platform for many enterprise applications.

With the growing emphasis on user experience and the growing popularity of the Web 2.0 concept (see Resources), more and more enterprises are considering building enterprise applications based on Web 2.0. Can a Domino user achieve this goal smoothly and quickly?

Commercially, Domino's existing customers and partners based on Domino Solutions are most concerned about the ability to quickly deliver WEB 2.0 Domino applications without adding to the existing investments, including people investment. From a technical standpoint, we know that Domino's programming model is slightly different from our common clear Web programming pattern, preferring a flat and mixed feature. For example, Domino's design element forms have both display and storage capabilities, which means that Domino developers must consider both front-end display and back-end data structures while building the system. In Domino's traditional programming mode, other experienced front-end Web developers are often difficult to directly participate in the corresponding Domino development team, to achieve effective division of work development. In addition, Web 2.0 development has more emphasis on front-end Web presentation and the user experience it brings, and the existing Domino Designer is slightly inconvenient when developing and debugging front-end code. While purely technically, Domino fully supports the development of WEB 2.0 applications under the existing programming model. In practice, however, these factors (flat mixed programming patterns, Domino Designer inconvenience to Web UI development debugging, and the difficulty of directly and effectively introducing independent front-end Web developers for collaborative development) lead to rapid building of high-quality, massive and flexible Domino Web 2. 0 applications often have many difficulties.

How to eliminate bottlenecks in the development of High-quality Domino WEB 2.0 enterprise applications by existing Domino developers? How can other front-end Web developers be able to join the development team of Domino Web 2.0 applications for effective collaborative development? How to simplify the cooperation process between the two types of developers, and finally facilitate the rapid implementation of system integration and deployment?

On the basis of summarizing previous projects, this paper introduces the best practice of developing Domino WEB 2.0 application. These best practices cover the entire lifecycle of system development. The second section describes the transformation of the programming model and the division of labor among developers during the design phase of the system. The third section will cover some common problems in the implementation phase of the system, and how to choose the most suitable implementation in combination with Domino's own characteristics and WEB 2.0 application characteristics. The fourth section describes how to implement efficient code assembly and flexible deployment of the system.