SOA is a Service Oriented Architecture, SOA is a mode architecture, and SOA implements currently there are currently a variety of options: Web Services, CORBA and JINI. therefore,
WebServices! = SOA.
Industrial companies such as IBM, Sun and BEA have been announced that the middleware has ended, and the SOA era is coming; and the MiddleWare, which represents the famous THSERVERSIDE.COM website represents the open source community, does not take advantage of: The idea that the middleware has become history is like It is said that the railway, road or waterway is the same, and the middleware is the future.
What is the middleware? Why have there be an argument to the end of the middleware?
J2EE (EJB) is a typical middleware that integrates important core functions of the business system, such as distributed computing power; transaction mechanism; security permissions mechanism.
At the beginning, people asked why the middleware advocate gave people such a scenario: if you are an IT software engineer of a large manufacturing company, when you start building a corporate information system, it will involve the user's rights system. Key system design such as cache performance system, constructing these basic technologies by enterprises, this will lead to key transfer of enterprise IT department work, because these systems need strong technical strength, therefore, the system for developing these general nature will give Enterprises bring huge risks.
Entrust these key basic functions with universal nature to professional company, and enterprise IT departments can, for example, BEA will position WebLogic in the corporate platform, integrating powerful middleware functions such as workflow.
In the JDONSD framework for me, this is a software development framework that speeds up J2EE development, shortens the J2EE development cycle, which is very interesting to such framework products, but found some problems in the actual communication process: I hope I can try this software. Customer trial involves code security, as long as the code is copied to the other party's computer computer, there is a possibility of decryption, so this issue is currently no perfect solution.
How to provide a JDONSD framework to provide to a customer service in a rental manner, customers do not need to copy the JDONSD framework code, as long as they connect the JDONSD framework server, this similar way to provide a virtual host will implement software companies and customers win-win, In this way, the J channel can implement a special feature service, which is the reason for the birth of SOA (Service Oriented Architecture).
So exciting SOA era is about to begin, it is clear that MiddleWare has not been wrong, SOA is at least based on high quality middleware functions, no excellent, reusable, scalable middleware, how can it be so much different Terminal customers provide services?
Let's take a look at the authoritative Sun's president Jonathan Schwartz attacks the disadvantage of middleware:
The first is the technical route messy, such as from the authorized authentication to the portal portals, from the web services to cluster Clustering, no basic standard or integrated interface, each project has a different set of companies, here, I inserted, Java world There are too many choices that everyone brought, just a J2EE or EJB standard is not enough to unify all software application areas, because there is a long way to go from J2EE standard to specific applications, which is also the reason for the framework of JDONSD. The location. Secondly, the pricing problem, the sales of middleware is also a traditional software form of sales, so there is a disadvantage of traditional software sales, such as computing, each cluster point or press each portal, each mailbox, etc., actually, these Individual units are built on a platform for a shared service, so if a customer needs a mailbox, the overall price is undoubtedly expensive.
Finally, Licensing is always raised to three times more prices for software systems that can be applied to Internet technology, which hinders the development of shared services. I helps customers recommend SAP's set of local network-based storage systems only need to be around, while Internet technology is required to do hundreds of thousands. Isn't it just connected to the Internet? As for the price?
Take a look at how the above problem is solved?
In the SOA era, the software function pricing will pay for $ 100 at each employee, as long as the employee pays $ 100, he can use all the service functions without limitation.
Let us listen to what other experts say, Powerbuilder laid David Litwack, said:
There is no doubt that in the SOA era, we will have a variety of applications, integrated applications and portal servers, content management systems, policies, and workflow engines; directory and metadata; identity authentication providers; proxy services, etc. The middleware, but from a market perspective, the middleware will disappear, why? Because these stuff mean only means a endpoint, it is not necessary to buy a vaporizer for a vaporizer, and people don't have to buy a vaporizer, and the vaporizer means that one endpoint is to buy a car.
The SOA application is equivalent to a car, we will make more transparent middleware, which is more likely to be submitted to SOA applications, which will be a new world.
