The Carbon Story

WSO2 Carbon Middleware à la carte December 2008

From traditional SOA products ..
Commoditization, followed by customization, are symptoms of maturing markets. Enterprise middleware has unfortunately not benefited from this pattern, yet.
Major vendor SOA products have good technology, but they have been cobbled together by acquisitions over time. The result is bloated, complex components that fit poorly together.
The objective of SOA is the development of loosely-coupled, interoperable network of services, that can be published, discovered and invoked in novel ways.
It is time that SOA middleware took some of its own medicine!

.. to WSO2 Carbon
With a componentized, customizable SOA platform, you can adapt the middleware to your enterprise architecture, rather than adapt your architecture to the middleware.

What is WSO2 Carbon?
A component-based SOA platform based on Equinox and OSGi
A new release of each of our current server runtimes:
Web Services Application Server 3.0
Enterprise Service Bus 2.0
Registry 2.0
(Mashup Server and Data Services coming 3 months later)
Also coming soon, a new Carbon based product: Business Process Server – our entry into the BPM market
Still very closely based on Apache technology: Apache Axis2, Apache Synapse, Apache ODE, Apache Tomcat and more
A well defined component model for Enterprise SOA Middleware

OSGi
Originally designed as a modularity model for embedded and mobile devices
Increasingly used as a framework by Enterprise Middleware
Spring dm Server
IBM WebSphere
JBoss AS etc
Provides several important capabilities:
Modules / Bundles as a more granular aspect than a package
Versioning
Dynamic loading support
SOA for the infrastructure – using a service model within a JVM

What motivated this?
Customers were increasingly using multiple parts of our platform together in ways we hadn't envisioned
For example, a major Management Software Vendor is using our WSAS, ESB, Registry and Business Process Server to fully integrate multiple legacy products
Two major issues:
Our “product” categories sometimes don’t fit customer requirements
We were copying code from WSAS to ESB to Data Services
OSGi gives us a standard component architecture
WSO2 Data Services 1.0 release in September was our “foot in the water” - now we're in all the way!

What is WSO2 Carbon? OSGi

Core Carbon framework
Typical Carbon core consists of bundles performing central functionality such as security, management, clustering, caching and more
The core itself can be customized. Use core components of your choice, leaving out the ones you don't need in your SOA
Products are built by adding components to this core
Security Mgmt Admin UI Bundle Mgmt Clustering Transports Stats

Enterprise Service Bus
ESB adds mediation, proxy management, tasks and more as well as registry core
Security Mgmt Admin UI Bundle Mgmt Clustering Transports Stats Tasks Proxy Message Mediation Core Repos

Web Services Application Server
WSAS adds service hosting, JSR 181 support and more to the core
Core Repos Data Services Data Source Mgmt DS Wizard JSR181 Service Clients Service Hosting Security Mgmt Admin UI Bundle Mgmt Clustering Transports Stats

The full component repository
Any product can add any component to customize itself to meet customer architecture requirements!
Instance UI BPEL Runtime Process UI Tasks Proxy Message Mediation Script Services Gadgets Scraping AtomPub SOA Govern Core Repos Data Services Data Source Mgmt DS Wizard JSR181 Service Clients Service Hosting Security Mgmt Admin UI Bundle Mgmt Clustering Transports Stats

Powered by OSGi
OSGi is the underlying core modularization technology
Shipping with Eclipse Equinox by default
Can be supported on Spring dm Server, Felix and Knoplerfish if required
Uses the core OSGi approach to support plugging in new function in a managed way
Any OSGi bundle can be deployed (e.g. ActiveMQ)
New components can be deployed into an existing installation
Used for both server runtime as well as for componentized management console
Customers can write and deploy their own OSGi components

But much more than just OSGi ...
Analogies:
Eclipse uses OSGi but is much more – it defines how you plug Tool components into a Tooling Framework
Microsoft Office uses DLLs, but is much more – it defines how you can share a graph component across multiple document types
Carbon uses OSGI, but it really defines how you build a consistent SOA platform
New service types plug into the console
Security, throttling, stats, TryIt, all work on any service component
Not just using OSGi for componentizing a single product, but rather entire middleware platform: app server, ESB, process server, registry, governance, mashup and much more

WSO2 Carbon product platform
Our “products” are now simply our choice about how you start with this platform
You can assemble your own “products” by combining components and deploying them in your preferred architecture!

Comparison with proprietary SOA platforms
Common patterns apply across all components
Need to understand many complex products
Skills
Designed consistently
Integrate at the JVM and configuration level
Spend time integrating vendors’ products not your applications
Integration
Install new function into an existing deployment
Same Admin UI for all components
Building platforms by acquisition has meant boundaries between components
Continuity
Choose what you need
Total platform < 150Mb
Designed for distributed deployment
Large monolithic products encourage centralized deployment
Deployment
Start simple and grow
Heavyweight
Difficult to install and configure
Agility WSO2 Carbon Proprietary

Use case: POJO service and logging
Anna is a POJO Service developer
She has an existing POJO service
The analytics department would like her to send a copy of every service request to them
She could write a new Handler in Java, but she discovers it takes 5 minutes to deploy and test the ESB Clone Mediator
Security Mgmt Admin UI Bundle Mgmt Clustering Transports Stats JSR181 Service Clients Service Hosting Message Core Repos Mediation

Use case: Data service and mediation
Daniel is a Database Administrator
He has used WSO2 Data Services to expose his Data as Secure Web Services across the Enterprise
Now he has been asked to implement an existing schema
By adding the Mediation component and using XSLT or E4X he can effectively convert the existing service interface to match the corporate schema
Security Mgmt Admin UI Bundle Mgmt Clustering Transports Stats Transform Data Services Data Source Mgmt DS Wizard Core Repository

Summary
WSO2 Carbon is a significant jump forward in Enterprise Middleware
All the benefits of OSGi, but considerably more
A complete SOA platform in Open Source
With major benefits over proprietary software
The core runtime is proven in major existing production deployments
Highly adaptable to real SOA deployments

WSO2 Carbon .. Middleware à la carte!
Adapt the middleware to your architecture,
not your architecture to the middleware.

Want it?!
Get it from http://wso2.org/
.. 100% open source under Apache License 2.0
The open source SOA company

http://wso2.org	1534
http://www.dimuthu.org	239
http://blog.afkham.org	78
http://www.tyrell.co	54
http://www.keith-chapman.org	43
https://wso2.org	16
https://www.wso2.org	15
http://tyrellperera.blogspot.com	12
http://www.slideshare.net	6
http://afkham.org	2
http://translate.googleusercontent.com	1
http://cncc.bingj.com	1
http://ruwansblog.blogspot.com	1
http://wiki4web.com	1
http://blog.ruwan.org	1

The Carbon Story

by WSO2

Accessibility

Categories

Upload Details

Usage Rights

15 Embeds 2,004

Statistics

The Carbon Story Presentation Transcript