Content Management System (CMS) News, Reviews, Events and Analysis.
 
 
 

SharePoint vs Alfresco: A Platform Perspective

In our February article entitled Under the Covers: Alfresco's SharePoint Services (WSS) Killer we looked at Alfresco's (news, site) take on providing basic document and collaboration services for free. Alfresco's project is called Alfresco Share

When we posited that Alfresco Share was after SharePoint Services' marketshare, it sparked a bit of chatter — some positive, some not so much.

Voices in the SharePoint camp said that the two solutions should not be compared, that SharePoint  was a platform — much more than a simple collaborative document management solution, whereas Alfresco was only providing some services.

While we believe the comparison was fair, we also agree that there's more to SharePoint than immediately meets the eye. By the same token, there's more to Alfresco than just Share, much of which we eluded to in the article.

Is it worth it to look at a side-by-side view of SharePoint and Alfresco from a platform perspective? Is it possible that one is significantly better than the other? Maybe, but the answer you get may not be the one you expected.

Eyeballing a Platform

When you review a solution from the platform perspective what kinds of things does one look closely at?

  1. The technology stack used
  2. The APIs, web services and protocols supported
  3. Office/productivity suite integration
  4. Application development tools
  5. Existing third party integrations
  6. The health of the ecosystem

This is not a review of pricing or support. Nor will we comment on whether it's easier to develop on one or the other. On those topics, you will have to find your own way.

The Ten Thousand Foot View

Both Alfresco and SharePoint are considered platforms, not simply products. This means their functional scope is intended to be expanded by the owner — either via custom development or via third party integration. No one considers either of these products black box tools which cannot be modified.

SharePoint Overview

SharePoint is comprised of two primary components. First you have Windows SharePoint Services (WSS). WSS is the foundation of SharePoint and as you can see in the diagram below includes all the core capabilities. WSS 3.0 is free. You can download, install it and be on your merry way.

If you want a little more "out of the box" functionality (and you have a budget), then you move forward and buy Microsoft Office SharePoint Server 2007 (MOSS).

MOSS builds on WSS, giving you six pillars of core functionality. For more information on MOSS' core functionality, see our article SharePoint 2007 Review - Six Pillars of MOSS.

WSS is the key to understand the platform take on SharePoint. It, of course, is built upon Microsoft servers and technologies such as the .NET framework, SQL Server and Windows Workflow Foundation.

SP_PlatformView.jpg
The SharePoint Platform
 

Alfresco Overview

Alfresco is a dual license, open source enterprise content management system. At its core is the Alfresco JSR-170 content repository. You build on that repository using a number of development approaches including REST, SOAP Web Services, CMIS, Java and the MS Office SharePoint protocol.

On top of the Repository is where all the Alfresco content management solutions sit, including Share, Document Management and Web Content Management.

AlfrescoPlatfomrB.JPG
The Alfresco Enterprise CMS Platform

There are 2 flavors of Alfresco, with 3 corresponding source code licenses: Alfresco Labs — the free community version licensed under GPL or if embedded in a commercial product licensed under an OEM Commercial License, and Alfresco Enterprise — the enterprise version that you get via subscription, also with a commercial license.

The Technology Stacks

SharePoint is a Microsoft solution. It therefore sits on a complete Microsoft stack including Windows Server, SQL Server, Internet Information Server, etc. There are no options here.

Alfresco on the other hand is said to run on just about any stack that can support Java. So while they likely encourage an open source stack such as Apache, Linux and MySQL, the platform can also be installed on Microsoft Windows Server and use MS SQL.

APIs, Web Services, Protocols

SharePoint sits on a Microsoft stack, so one develops SharePoint solutions using Microsoft technologies — ASP.NET, WCF, SOAP-based Web Services, XML and so on. For Rich Internet Applications (RIA) you have Silverlight and ASP.NET AJAX.

To develop solutions for Alfresco, you have scripting languages like JavaScript, PHP and Freemarker, and Java. The repository is accessed via REST API, Web Services, SharePoint Office Protocol and a number of other standards. Both platforms support RSS and WebDAV.

Of course the Content Interoperability Specification (CMIS) is also important to mention. Alfresco's latest versions support the currently proposed implementation, and have demonstrated that in a number of ways. SharePoint does not yet implement the standard itself — we expect to see that in SharePoint 2010 — but Microsoft is supportive of CMIS and have demonstrated how MOSS currently can integrate with another CMIS-compliant repository.

Office Integration

One would have thought that this is an area that SharePoint would win hands down, but it that's not the case. Microsoft opened the doors to interoperability when they released MS Office and SharePoint's technical specifications to the broader public.

This move has enabled Alfresco to implement their own SharePoint Office protocol. So one can talk to Alfresco Share through MS Office just as easily as you can communicate with SharePoint.

Application Development Tools

Aside from the fact that you can write code for either application using your basic text editor (only for hard core geeks), each vendor offers a couple of ways to develop solutions and/or customize their platforms.

Microsoft has both SharePoint Designer (now free) and Visual Studio 2008. Alfresco has Eclipse (although they say it's not needed that often) and their new Web Studio.

Web Studio is a designer for Surf — Alfresco's web application and site assembly framework. It is Surf that Share is built upon.

You can compare Web Studio to SharePoint Designer and Visual Studio to Eclipse. Arguably there are solid development tools on both sides of the fence here.

Full API Access

Both Alfresco and SharePoint are platforms. Therefore, they provide full access to the core APIs so that you can both customize the platform and build solutions that integrate with it.

With SharePoint there are over 3000 APIs to potentially work with. We don't how many API's make up Alfresco, but we bet there's at least as many as SharePoint has, give or take a few.

Third Party Integration

It's probably a safe bet to say that you know about many of the third party integrations with SharePoint. There's hardly a day that goes by when we're not talking about a new integrated solution offering for SharePoint. You can also pick up any number of web parts or other add-on components to extend SharePoint's capabilities.

Whether it's for collaboration in the form of blogs, wikis, activity streams, enterprise content management, communities, content connectors, there's something out there that you may need to take advantage of.

For its part, Alfresco has a healthy ecosystem out there building third-party add-ons for the platform. But they also have relationships with other vendors who offer integrated solutions that may be preferred over what they offer within the platform themselves.

The Health of the Ecosystem

The SharePoint Ecosystem

There's a reason SharePoint is so attractive. WSS 3.0 is so easy to install, configure and start working with. That's why it has taken off so quickly and gone so deeply into the enterprise. The fact that it sits on a Microsoft stack is probably more of a plus than a minus – whether you like it or not.

But Microsoft has also been very smart in how they have positioned SharePoint and how they have encouraged the broad creation of integrated solutions to extend the SharePoint platform.

Which leads us to the SharePoint Ecosystem. The SharePoint Ecosystem is a combination of services, add-ons and integrated solutions offered by the greater SharePoint community.

SPEcosystem.jpg
SharePoint Ecosystem from CMS Watch SharePoint 2009 Report

SharePoint thrives on its ecosystem. Its community of vendors and individuals extol the virtues of this platform. The ecosystem takes the platform and extends it in ways Microsoft probably only dreamed of.

If that ecosystem was to disappear, there would be greater opportunity for a competitor to come in and take market share.

The Alfresco Ecosystem

You can easily differentiate the SharePoint Ecosystem with that of Alfresco's. As an open source platform, Alfresco has — as we've said — both a commercial and community version. The Alfresco community is dedicated to developing add-on components for the Alfresco platform

Alfresco does have a large community, but they don’t seem to depend on it for their success. One data point here is recent commentary from Alfresco's Matt Asay:

"In open source, we tend to think of community as a group of people that actively contribute code to a project. But this myth was debunked years ago. Most people don't contribute any software, any bug fixes, any blog mentions, or any anything to open-source projects, including those from which they derive considerable value. They just don't."

If the Alfresco community went away, would Alfresco? It doesn't sound like it. But does community and ecosystem are not exactly the same thing. Community in the above sense is more the community of contributors to the software product.

When comparing the two ecosystems, it's fair to say that Microsoft had a big head start and continues to hold a significant lead over Alfresco. A simple search of Microsoft's partner directory shows 387 Enterprise CMS & Forms partners. Alfresco's website lists less than 30 Solution Partners (those who develop complementary solutions or embed Alfresco technology).

Can You Pick the Best Solution?

There isn't really anything in the platform comparison above that makes you think Alfresco is better than SharePoint. There's also nothing to make you think that SharePoint is better than Alfresco. And we certainly aren't believers in the open source vs proprietary bandwagon — there's room for both.

But the reality is, SharePoint is in there with a thriving ecosystem that Alfresco doesn't appear to duplicate. Yes, open source is making more in roads into the enterprise, but they are still going to meet SharePoint at the door. It's not impossible to push it aside and take its place, but it's an uphill battle that won't be easily won.

An Exciting Year Ahead

SharePoint 2010 is coming later this year. Microsoft have launched a SaaS version of SharePoint. Meanwhile Alfresco has been faster to deliver technologies like Web Scripts and CMIS. They seem to have a lot of interesting pots on the stove, and are putting more energy behind Alfresco Share marketing.

As these Enterprise CMS and Enterprise 2.0 tools evolve we'll be following. The Microsoft challengers have picked a tough fight and have not yet breeched the wall, but they're certainly banging on the gate.

 
Read More About:
, , , , , ,
 
Was this article useful?
 

13 Reader Comments

1 | Peter Morel — May 13, 2009 12:39 PM

I work as IT engineer with an international company with many subs world-wide.

We first selected Microsoft SharePoint until we realized that:
- It forced us to be 100% Microsoft compliant (and many subs already chose Linux and Open Office)
- It was VERY expensive (Each client must pay a CAL (Client Access License)
- We had to maintain 2 sets of documents:
the ones on Shared disks to be accessed by standard tools
The ones in SharePoint and NOT accessible by standard tools as SharePoints store them in an MS SQL Database
- One of our subsidiary stores VERY LONG technical files which cannot be entered in Sharepoint. We suspect due to a limit of size of BLOBs.
- We have to keep international versions (at least 7 languages) of the documents. SharePoint does not offer any tool for that
- We found that changing the structure of meta-data AFTER installation if a REAL MESS and this is a topic where changes count …

We then tested Alfresco.
It solved all the previous points and as we did it without informing our test users, none of them even noticed the change !
The only thing that misses compared to Sharepoint is the SharePoint Lists which is a sort of local database on the desktop but Alfresco say they will implement this feature too… Wait and see.

We are now close to the end of our tests and I would not bet a dime on Sharepoint….

Peter


2 | Jacob — May 13, 2009 1:19 PM

isnt the above a little too complex from the point of a small to medium sized business? wasnt the new wave supposed to shift focus away from IT and towards business? isnt services exactly what we want and not platforms. platforms may make sense for solution developers, or large enterprises which need highly customized solutions.

if we're talking about “sharepoint for enterprises”, talking about sharepoint as a platform makes sense. if were talking sharepoint for SMBs, we must talk in terms of services and features, and ease of use, and it is on those counts it must be compared with “sharepoint alternatives”

3 | Dave Lane — May 17, 2009 4:22 PM

The article above makes it sound like Microsoft “opened the doors to interoperability” in a fit of generosity, magnanimously allowing Alfresco to achieve some compatibility… Nothing could be further from the truth.

Microsoft was *forced* by the EU anti-trust case to release documentation for some of its fiercely protected interoperability formats. (see, for example, http://pcworld.about.com/od/microsoftantitrustcase/Microsoft-loses-appeal-against.htm)

It's only thanks to the EU (unlike the US) sticking to its guns and punishing Microsoft for ongoing flagrant anti-competitive practices that consumers actually have a choice… And look at how well Alfresco have done. It's great to see them eating Microsoft's lunch.

4 | Steve Odart — June 4, 2009 7:31 AM

What an interesting article! Equally, it was no surprise to read Peter Morel's comments.

We have been an Alfresco implementation partner for over 2 years now, and to date have implemented the solution in over 20 organisations and companies. The point is this, Alfresco is a bricks and mortar software company that happens to have an open source commercial model. Therefore there is an established eco system of system integration partners that are able to provide consultancy, implementation services and operational support.

In every scenario, we have found that our clients have selected Alfresco based on a functional assessment of its capability, and its fit to requirements. This tends to confirm the content of this article, in that Alfresco is a mature, extensive product that is worthy of evaluation for a given project, if Sharepoint is currently being considered.

5 | Christopher Creel — August 13, 2009 11:52 AM

We have been using Alfresco for about a year now. Our technology landscape is incredibly complex with a rich mix of different technologies including Microsoft and IBM. If your company is already locked in to a Microsoft stack and can afford the cost, Sharepoint does make sense. My experience is that such companies are hard to find these days (especially the part about being able to afford the cost). All these CMS systems have the same necessary capabilities. With IT costs becoming harder and harder to justify and CMS systems becoming commodities, Alfresco has the wind at their backs.

6 | Brokenspokes — August 26, 2009 11:20 PM

We are currently evaluating Alfresco for CMS duty. My organization recently implemented a system based mostly on Microsoft Sharepoint and custom-made components, but we ran way over budget. As a result, the system is slow, inflexible and doesn't have the necessary capabilities that we need. We can't afford to expand until, hopefully, next year. Not only that, there are people in our organization that use Apple computers, OpenOffice and Mozilla Firefox, etc but our CMS plug-ins don't work properly with anything but Windows and Internet Explorer. That minority was never consulted when the current system was being put in place. That is why my group is pushing for something like Alfresco (We are doing this against the wishes of some influential IT folks in our organization). Not only is it cheaper, but it is a more open and accommodating platform—that's very important these days.

7 | Gary — September 10, 2009 8:28 PM

We have been searching for replacement components to our increasingly expensive and partially broken Vignette stack. Alfresco vs SharePoint. The cost structure for both vendors is similar as freely stated by Alfresco reps. So, MS gets their $ on initial license purchase, CALs and upgrade costs, while Alfresco gets their $ by charging hefty support fees which continue year in and year out. So, it is not obvious which one is more expensive, because they both are quite costly, but in different ways.

8 | Can Bilgin — October 5, 2009 10:32 AM

We are a development firm, working different enterprise application implementations. In our last project, we were specifically asked to work with Alfresco and I must say, it is no where near the capabilties of Sharepoint. So I simply do not understand the comparison and the comments made. If you are going to use Sharepoint as simply a CMS, then you can also go with e.g. dot net nuke, however, if you are planning to implement it as a back bone to any network application that is going to run in your enterprise, I say go with WSS cause it is FREE. Here the real comparison has to be made between Alfresco and WSS not Sharepoint Server which is just an implementation over WSS.

9 | MOSS — November 21, 2009 9:19 AM

We first selected Microsoft SharePoint until we realized that:
- It forced us to be 100% Microsoft compliant (and many subs already chose Linux and Open Office)

Answer: “100000000 many end user using windows & Office”


- It was VERY expensive (Each client must pay a CAL (Client Access License)

Answer: “80 $ per CAL is a buck to many companys”

- We had to maintain 2 sets of documents:
the ones on Shared disks to be accessed by standard tools
The ones in SharePoint and NOT accessible by standard tools as SharePoints store them in an MS SQL Database

Answer: “It is FALSE, you can access shared document via file system to sharepoint Library”

- One of our subsidiary stores VERY LONG technical files which cannot be entered in Sharepoint. We suspect due to a limit of size of BLOBs.

Answer: “It is FALSE, you can modify the size files stores by default is 50MB per document”

- We have to keep international versions (at least 7 languages) of the documents. SharePoint does not offer any tool for that

Answer: “JAJAJAJA, It is FALSE, dowload the free languajes pack, to many lanaguages to exits in Office”

- We found that changing the structure of meta-data AFTER installation if a REAL MESS and this is a topic where changes count …

Answer: “It is FALSE, make a good definition to content types metadata”

10 | Really MOSS? — December 1, 2009 7:39 PM

Really MOSS?

- The fact that “100,000,000 many end user using windows & Office” does not mean that each and every company is a 100% Microsoft shop. It makes sense for some companies to branch out and use other solutions such as a Linux distribution and/or just OO.org.

- In my opinion (and I'm sure many other people's as well) “80 $ per CAL…” is not quite as cheap as $0 per CAL. Just because “many companies” can spend $80+ per CAL for a solution, doesn't mean that every company can. I know as a solution engineer, my manager and other business leaders like to spend as little as possible and still receive the same functionality.

- While it is true “you can access shared documents via file file system to sharepoint Library” maybe Peter was meaning other tools that his corporation has implemented cannot access the sharepoint directories. You know, he did mention that they weren't a 100% Microsoft shop. Maybe they were using some *nix based toolsets that couldn't access the shares…

- Yes, you can modify the default sizes of documents.

- Language packs are a pain.. Language packs typically don't localize all functionality (I don't know about Sharepoint as I've not utilized the language pack functions of it).

- Metadata structure should be well-defined from the beginning.. however, if completely messing up your document structure by changing minor parts of the metadata structure is a really big issue.


Your comment reeks of fanboy-ism. I'm not a fan of either Alfresco (never really used it) nor of Sharepoint. Each system has it's pros and cons; however, when you're trying to refute someone else's argument points in a comment, not speaking like a 15 yr old will go a long way in reinforcing your own argument.

11 | techieg — December 9, 2009 2:35 PM

Well, with SharePoint Online - http://www.microsoft.com/online/sharepoint-online.mspx , it has never been cheaper especially since you do not have to break out your wallet for any equipment, installation, and administration. At just $3.99 per user/month. Even cheaper when you go with the complete productivity suite http://www.microsoft.com/online/business-productivity.mspx , at just $10/user/month.

12 | logic — December 10, 2009 5:19 PM

Content aside, the article's purpose is to sell advertising..scroll down….thanks


13 | Gunnar Langeland — January 15, 2010 4:28 PM

Sharepoint is a good tool, for many things. What it is not good for is worging as a CRM / CMS / Document Management / Project Managment tool!!

How come? Well first off:

- (technical) -> Painfully slow outside the organizations LAN (over the Itnernet). Uses postback (click, enter, click, save etc.). Yes, AJAX can resolve some, but how big is your development budget?

- Easy to install, easy to backup; A MESS to administrate, integrate, maintain, and restore (yes I know it has a recyckle bin..). If your company has more than 10 employees, and you want to put “all your stuff” into Sharepoint and customize it, just hire a Sharepoint guru (50 000 $ a year for a good one)

- Saving your data in a database???? Who thought of this? The development department must have had an insane momemt! Put files on disk, that gives you all the options you want for backup, restore, indexing (yes I know of the options even with Search Server 2008 Express), syncronize files to integrated systems (yes SQL Server Integrated Services can do it for you, but has anyone tried it and looked at the time spent for a solution you can trust??)

So.. If your organization is less than 20 people, data loss and data mess is not an issue, and you want to move your Excel “databases” to a web interface, go with Sharepoint.

Everyone else go with Alfresco or Sosius for smaller companies. Alfresco simply worsk so much better.

Don't believe me? Then do this:

- Have your most skilled IT person set up Sharepoint WSS (free version). Create a site, a couple changes and publish it. Ask users to insert data into the lists. Then have them play with it. Then start creating your reports. Then see how you can deploy changes in one site to another server (using VM Ware or Citrix XenApp virtual server for this test would be great). When you figure out the test has given you little and cost a lot (mhrs wize), stop!

- Do the same test with Alfresco, and see the difference!

Personally I have spent 2 years with Sharepoint and 3 months with Alfresco. Moving from Sharepoint to Alfresco feels like crawling out of a mud hole, onto a sunny beach where everything is just sunny and bright!

But why is Sharepoint selling, and so many companies using it? Well, Microsoft has a good plan, and the best sales persons in the world (well, many of them). It is also safer for a manger to say “We went with the know technology”. That is why. Ask all those companies that went with Sharepoint, how much they spent. And also ask them what they have gained.. They will never tell you, to many mangers will loose their jobs..

It's up to you, I am glad we moved away from Sharepoint.

Leave a Response

  Remember me?

Related Enterprise CMS Articles

 

From our Job Board  View all jobs | feed Jobs RSS feed | Post a job right now

 

Featured Events  View all events | feed Events RSS feed | Add your event

STAY UP TO DATE
Subscribe to our RSS feed...
SUBSCRIBE TO OUR RSS FEED