what exciting news! BTW, which tech will be the basis, so that I can start up
now :D
Vincent
From: Sameera Jayasoma
Date: 2013-11-28 15:01
To: architecture; WSO2 Developers' List
Subject: Re: [Dev] Carbon 5 (C5) - The next generation of WSO2 Carbon Platform.
Here is the milestone plan for C5.
M1 - December 06, 2013
Migrating to Equinox Kepler
Centralized Logging-backend
Moving the codebase from SVN to GIT
Basic C5 runtime
M2 - December 20, 2013
User API design and implementation
Carbon Deployment Engine
M3 - January 23, 2014
Carbon Clustering API and Implementation
Pluggable Runtime Framework
Configuration and Context Model
Repository API and implementation
M4 - February 07, 2014
Improved Patching model
Plugging Tomcat to C5
M5 - February 21, 2014
RESTFul admin services framework
Jaggery based UI framework
Per tenant security manager and Thread monitoring
M6 - March 14, 2014
Composite application model for C5
Plugging Axis2 to C5
Improved Feature Manger implementation.
Thanks,
Sameera.
On Wed, Nov 27, 2013 at 5:44 PM, Sameera Jayasoma <[email protected]> wrote:
What is C5?
Carbon 5 will be the next generation of WSO2 Carbon Platform.
Why C5?
The existing Carbon platform has served as a modular middleware platform for
more than 5 years now. We've built many different products, solutions based on
this platform. All the previous major releases of Carbon were sharing the same
high level architecture, even though we've changed certain things time to time.
Base architecture of the Carbon is modeled using the Apache Axis2's kernel
architecture. Apache Axis2 is Web service engine. But it also has introduced a
rich extensible server framework with a configuration and runtime model,
deployment engine, clustering API and a implementation, etc. We extended this
architecture and built a OSGI based modular server development framework called
Carbon Kernel. It is tightly coupled with Apache Axis2. But now Apache Axis2
is becoming a dead project. We don't see enough active development on the
trunk. Therefore we thought of getting rid of this tight coupling to Apache
Axis2.
Carbon kernel has gained weight over the time. There are many unwanted modules
there. When there are more modules, the rate of patching or the rate of doing
patch releases increases. This is why we had to release many patch releases of
Carbon kernel in the past. This can become a maintenance nightmare for
developers as well as for the users. We need to minimize Carbon kernel releases.
The other reason for C5 is to make Carbon kernel a general purpose OSGi
runtime, specialized in hosting servers. We will implement the bare minimal
features required for server developers in the Carbon kernel.
Our primary goal of C5 is to re-architect the Carbon platform from the ground
up with the latest technologies and patterns to overcome the existing
architectural limitations as well as to get rid of the dependencies to the
legacy technologies like Apache Axis2. We need to build a next generation
middleware platform that will last for the next 10 years.
When can you expect C5?
We have already started working on C5 with a dedicated team of 5 members for
three to four months. We are planning to complete the bare minimal components
of C5 by March, 2014. Once we get to this stage, our products teams can start
migrating their components to this new architecture. I will share the detailed
milestone plan shortly.
Thanks,
Sameera.
--
Sameera Jayasoma,
Architect,
WSO2, Inc. (http://wso2.com)
email: [email protected]
blog: http://sameera.adahas.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
Mobile: 0094776364456
Lean . Enterprise . Middleware
--
Sameera Jayasoma,
Architect,
WSO2, Inc. (http://wso2.com)
email: [email protected]
blog: http://sameera.adahas.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
Mobile: 0094776364456
Lean . Enterprise . Middleware
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
