Component-oriented development: SCA or SOA? __soa

Component-oriented, new generation of software development models and methods. So what are its norms and standards? Now the answer is getting clearer:SCA. To answer this question, perhaps most people will now say SOA, in fact ' SOA ' is the wrong answer! (Does it seem that the current software world lags behind SOA?!) But on this issue ' SOA ' is indeed the wrong answer. SOA is not a method of software development, it is not the standard of software development. He is just a larger concept of software architecture, with a vague connotation and an ultra strong extension, just like the word middleware. SCA is different, it has clear connotations and normative standards, of course, SCA is within the vast scope of SOA, but more realistic significance.

It can be said that with the beginning of the July Sun Company joined the SCA/SDO International component Standards Organization, marking Java and EE will gradually in the next five years, the "solution of key customer critical issues of the mainstream technology" status. And as Sun joins SCA/SDO, Java/javaee's customer value leadership is on the move, and Java EE application servers will enter a time of low value and homogeneity. Sun Company later in Primeton Software (Primeton Technologies) to join the organization, is illustrated two: first, in the fierce ideological struggle, joined representatives to recognize the loss of leadership status, the second is to gradually give up their own jbi. But a discerning eye will know that not joining will mean recreating a more than 10-year-old Novell and entering the marginalized market.

Java EE's efforts in the marketplace have also been around for some time, and they are still playing the "mainstream technology of solving customer key problems" in the new Generation (Sca/sdo/bpel) technology, but they have become more and more inadequate in recent years. Directly leads to the emergence of a whole host of diverse technologies to compensate for their deficiencies: Spring, Struts, Hibernate, AOP ... These 2.5G technologies have solved some problems over a period of time, but they are also causing more problems (integration, open source, and so on).

Sca/sdo/bpel is the new decade of software development of the mainstream technology, is the software development 3G era, is the mainstream is he is in a thorough solution to the new ten-year customer key issues. In the future, Java/javaee will become a homogeneous platform for enterprise operation, which solves the problem of distributed computing, and is also a mature platform, just like PC and operating system, the development is slow. Other ' 2.5G ' technologies (Spring, Struts, Hibernate, AOP ...) will be integrated into the ' 3G ' (Sca/sdo/bpel), and will gradually withdraw from the independent development of the market, and Sca/sdo/bpel is rapid development, and constantly solve the customer's key issues:

1. Application development and integration efficiency-〉 business responsiveness and low cost

2. Application of modular reuse, change maintenance and management-〉 application of asset value promotion and on demand

3. Open, standardized, high-performance and application monitoring-〉 enterprise-level operational and management capabilities