1, advantages:

EOS has its own theoretical basis: component-oriented. The so-called component-oriented is to define a structure (which can be considered as a function). In the structure, define the input and output, and a component is formed.

For each Http access, a ThreadLocal variable will be created, in which an xml tree will be stored. During the running of this thread, the nodes in the positioning tree will be added, modified and queried continuously. This process is implemented using xpath. It is said that xpath part is rewritten by themselves, in order to improve efficiency;

EOS development is very convenient. It defines many components, such as database storage components (actually a set of static sql methods), which can complete a function only by drawing. So its development speed is very fast;

EOS has a complete debugging, publishing and management mechanism, and it even has its own server, so it is more convenient to manage.

EOS has an embedded workflow system, which can complete workflow design only by drawing;

Components can be easily published as webservice, and simple database-based web applications can be easily developed.

The components provided are strictly tested by the manufacturer, so they are very safe to apply, and the graphical tools reduce the possibility of many mistakes;

2. Disadvantages:

From the perspective of technology and employee development, people who use it feel that their job-hunting competitiveness is disappearing a little bit;

From the perspective of tools, EOS is at best a development platform, not the SOA business platform it boasts, and all business development can't provide any available business framework. EOS developers should sum up blood and tears before development;

From a systematic point of view, there is no possibility of value transfer in things developed on EOS. It is absolutely impossible for you to develop a satisfactory module on EOS and use it in other non-EOS projects. This is a disaster for a company or individual who wants to accumulate;

Compared with traditional object-oriented and J2EE development, EOS is easy to use and has a short learning curve. But this is controversial, EOS knowledge is not universal.

The development of EOS pages is inconvenient, although RIA's support is not as good as it boasted. Now EOS5 is the most widely used version on the market. This version was published in 2005. It was good that the WEB development platform was so strong at that time. At present, EOS6 released this year, not to mention international, at least no one in China can match it.

On the surface, there is little difference between EOS5 and EOS6, both of which are component assembly. In fact, there is a big difference: using XML for data transmission in EOS5, and using JAVA objects in 6, the performance will have a qualitative leap.

In addition, he meets the standards of SCA and SDO, at least he can show that he is an open thing, not behind closed doors. If the software is to standardize business, EOS is still good; EOS is worthless if the software is to be ravaged by users or decision makers.

Extended data:

PrimetonEOSPlatform is an SOA application platform. PrimetonEOSPlatform is based on J2EE, Eclipse and other open technologies and platforms, adopts advanced SOA architecture and standards, and adopts component, graphical and integrated platform products.

It provides life cycle support for building SOA applications from design, development, debugging and deployment to operation, maintenance, control and governance.

EOS Studio: EOS Studio is an integrated development environment, which integrates the design, development, assembly, debugging, maintenance, deployment, management and release of component-oriented applications, and provides the development, maintenance and management of SOA applications and services in the whole life cycle.

References:

Baidu Encyclopedia -Primeton EOS Platform