Visit the WSO2 ESB project page to see more information on this great invention, or you could directly go to the download page. This time we are releasing the documentation as a separate bundle and hence the samples guide and all the relevant documentation will be available on the documentation artifact.
Release note will give you a better understanding on the WSO2 ESB 2.0 while you could read more about it on the online documentation.
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
WSO2 ESB is a lightweight and easy-to-use Open Source Enterprise Service Bus (ESB) available under the Apache Software License v2.0. WSO2 ESB allows administrators to simply and easily configure message routing, intermediation, transformation, logging, task scheduling, etc.. The runtime has been designed to be completely asynchronous, non-blocking and streaming based on the Apache Synapse core.
WSO2 ESB 2.0 is developed on top of the revolutionary Carbon platform (Middleware a' la carte), and is based on the OSGi framework to achieve the better modularity for your SOA architecture. This also contains a lots of new features and many other optional components to customize the behavior of the server. Further, if you do not want any of the built in features, you can uninstall those features without any trouble. In other words, this ESB can be customized to your SOA needs.
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---WSO2 also releases a set of other SOA related products making the WSO2 platform completely an SOA stack for the industry. WSO2 WSAS is a web services application server, WSO2 Registry is the registry solution which also provides SOA governance and the WSO2 BPS which is the business process server to manage BPEL interactions. You may give them all a try.
Most importantly you could now add features from each of these products to WSO2 ESB just by adding the relevant components. In other words, all the features in this product stack are developed as feature components which are self contained so that by adding those component to any carbon server you could get that functionality on that particular server.
This lets you to “Adapt the middleware to your architecture, and not your architecture to the middleware”, which will be one of the turning points of the future of middleware applications.
Posts
3 comments:
Congratulations!
You had always time for my questions as a new comer to ESB although you were very busy. Keep up the good work.
Also known as Affero GPL or AGPL, this license was developed to deal with the services that are provided over the network (like google search) and as they are hosted and run at a server, they do not need to release the changes that they do on the free software projects. The Free Software Foundation has recommended that the GNU AGPLv3 be considered for any software that will commonly be run over a network.
The GPL is the most popular and well-known example of the type of strong copyleft license that requires derived works to be available under the same copyleft. About a year ago the third version was released, but there has been some projects that have stated to never move to the newer version (the most noticeable example is the Linux Kernel). In the GPL you may not link with code containing a different license nor release changes under a different license. This way, GPL license spreads by a virus in software projects. You may use GPL code as you like, but the changes you do or the software that is linked with the licensed software, must be also licensed as GPL.read to get more in Web Development USA
Post a Comment