The architecture of the NC is much more lightweight relative to Teems, at least the current preliminary feeling is like this. It is said that it is lightweight that does not mean how much content, but the degree of dependence on the NC architecture is applied.
Teems is a fully objective application architecture, including persistence, business applications, and user interfaces are completely objective. NC is somewhat different, which is not a complete OR mapping relationship in terms of persistence, but a traditional row record mode. That is, a table in the database corresponds to VO in an NC, and the association between Vo and Vo is in the VO in the form of PK. If the service application, an associated object is required, it is necessary to manually Load it. From the perspective of development, Teems's way is easier to develop and understand, while NC has better performance in performance (although it is not difficult to understand).
NC is on the persistent layer, which is DMO (Data Management Object), which is DAO mode, but DMO can pass the NC development tool to export database tables in the initial stage, automatically generate most of the code. Nc has the concept of VO, some similar to the BO in Teems, but not the same, VO is also passed, but Vo is just a simple POJO, and there is no business method. The business method of Vo is written on the BO in the NC. BO is a complete business method, which may be a VO, or multiple VOs, some similar to the concept of Business Service.
NC in UI, using the BS structure Applet program, with the advantage of TEEMS's CS structure. Three-layer structure is implemented by J2EE's servlet, and complex user interaction is implemented with SWing. In terms of UI structures, NC's inheritance system is much more lightweight than TEEMs, and the components and development methods are mature and improved than TEEMs. The NC's UI structure and layout are also lightweight, not so complicated, it looks more concise, but I don't know how the General's UI is.
NC's report prints, uses the NC reports and print components developed by themselves. Report and printing functionality by handling a small amount of database table and adjusting the secondary development tool similar to Excel. Although the ability to achieve very complex statements is limited, it is relatively very simple for most reports. Teems did not have its own report print scheme, at least the efficiency of the development is not as high as NC.
The code quality of NC, in the present, similar to Teems, most of the code is a copy of the paste. However, I think this is also the characteristic of these two architectures. Since the NC's inheritance system and implementation are relatively lightweight, the relative design and development is much larger. That is to say, a certain package and improvement relative to the NC architecture used on its own project is easier than TEEMS. The NC's code style is the same as Teems, which is relatively good, at least one large architecture. Although there are very many big-class and big ways, it is very easy to understand due to the format and content.
Summary, there is a common feature for NC and Teems, it is difficult to say that it is an advantage or shortcoming. Very engineering, suitable for a large number of people to develop, and the requirements for personnel are not particularly high. Technology is very traditional, there is no high threshold in technology, perhaps because of engineering and history, both architectures have adopted commercial immature technology and design development methods (I don't know if it is good or bad).
It is probably like this, and it will continue to analyze in the future.
