incubator-sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache Sling > Who is using Sling ?
Date Wed, 26 Aug 2009 15:29:00 GMT
    <base href="">
            <link rel="stylesheet" href="/confluence/s/1519/1/1/_/styles/combined.css?spaceKey=SLING&amp;forWysiwyg=true"
<body style="background-color: white" bgcolor="white">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="">Who
is using Sling ?</a></h2>
    <h4>Page  <b>added</b> by             <a href="">Ian
    <div class="notificationGreySide">
         <h1><a name="WhoisusingSling%3F-WhoisusingSling%3F"></a>Who is
using Sling ?</h1>

<p>Although Sling is a relatively young project, only recently graduated from the incubator,
it already has a growing following of adopters. This page lists those adopters. Being on the
community wiki, if you are using Sling and your not listed here, please add yourself with
a brief description of your project and a how you have adopted Sling.</p>

<h2><a name="WhoisusingSling%3F-Adopters"></a>Adopters</h2>

<h3><a name="WhoisusingSling%3F-SakaiProject%28"></a>Sakai Project (<a
href="" rel="nofollow"></a>

<p>The Sakai project is a project that was started in 2004 funded by a research grant
from the <a href="" rel="nofollow">Andrew Mellon Foundation</a>.
Its aim was to create an open source collaborative environment to support teaching and learning
and research within Higher Education. The initial project members were Stanford University,
University of Michigan, Indiana University and the Massachusetts Institute of Technology.
These four were rapidly joined my many other institutions growing to over 160 Universities
running Sakai in production today. The project funding has come to an end and sustainability
has been achieved as a result of community contributions.</p>

<p>The University of Cambridge (UK) was one of the early adopters and rapidly became
involved in shaping the core of Sakai. In early 2008, shortly after Google made its OpenSocial
announcement a decision was made to re-architect Sakai to be more user focused and socially
aware, building on the collaborative experiences seen in networks like Ning and Facebook.
After a period of evaluation Sakai chose Sling as its core technology partly because it had
the solid backing of the Apache Foundation, but also because it was based on OSGi for componentised
development, solid REST semantics and a solid JCR production backend in Apache Jackrabbit.</p>

<p>This adoption has had a huge impact on the Sakai code base. Although the core development
is not complete, Sakai's line count has dropped from about 1.8M lines of code to about 200K
as Sling has replaced many of modules that satisfied the Enterprise Content Management use
cases. As a result, the code quality, scalability and performance have all risen whilst the
memory footprint of production JVM's has halved. Perhaps the most startling impact has been
the new ease with which UX designers and UI developers are able to work with the framework,
where previously the Java web environment had precluded a UX/UI driven rapid development cycle.</p>

<p>Sakai 3 based on Sling will be going into production at the University of Cambridge
by December 2009, with a number of other early adopters. For more information see an early
<a href=""
rel="nofollow">screencast</a> or look at the project site (<a href=""
rel="nofollow">frontend</a>, <a href=""
rel="nofollow">backend</a>) or <a href="" rel="nofollow">live
demo</a> </p>

<p>License: ECL2/Apache2</p>

    <div id="commentsSection" class="wiki-content pageSection">
       <div style="float: right;">
            <a href=""
class="grey">Change Notification Preferences</a>
       <a href="">View
       <a href=";showCommentArea=true#addcomment">Add

View raw message