Quick start of the Java EE

background of the birth of Java EE

Under the traditional development model (single-layer application structure), the following fatal disadvantages are prevalent in the application:

-Data, pages and business logic in a logical hierarchy, the function is tightly coupled;-code reusability is very low, maintainability is poor;

-High application coupling, no scalability at all;

-Any minor feature updates that need to be redeployed for the entire application;

-Changes to the background data structure will result in all relevant code changes;

-Database connection management is a big bottleneck.

An enterprise needs an application architecture that meets the following criteria:

-The framework and structure of distributed, portable components;

-simplifies the design of server-side middleware (including transaction processing, security, etc.);

-Provide standard, open APIs for components, applications, and server-side.

2 Intentions of the Java EE:

-For enterprise users, the Java EE is a set of open standards platform, join this platform, all business systems within the enterprise can be run in different operating system

and different environments, thus forming a complete set of enterprise application systems.

-For developers, the Java EE is a ready-made solution, and many bottlenecks in the development process, such as transaction handling, security, and migration value, will

Solve the logic level separation, realize the distributed application.

definition of the Java EE-is an open, standards-based platform;

-is a web-oriented, server-centric, enterprise-class application for developing, deploying, and managing N-tier architectures.

java EE architecture diagram

Basic Technology standard of the Java EE

JavaBEAN: A reusable component that can be visualized in a programming environment, where the programming environment includes: Ides, such as Eclipse.

JDBC: Is the Java API used to execute SQL, providing Java with a common way to access different relational databases (DBMS). And our commonly used micro-

The soft-provided Access database is the same as API--ODBC.

JNDI: Contains API and SPI (Service Provider Interface), JNPI SPI is used for naming directory service design and implementation, so that all kinds of data services standardization;

This Java provides quick and easy access to any directory service through the Jndi API.

RMI: Distributed invocation based on TCP/IP sockets is the basis for Java development of distributed applications.

The world of Java is just getting started, and I look forward to understanding it more thoroughly in the next study.

Quick start of the Java EE