I started working with Alfresco back in 2005 and the code base was a lot smaller back then! More recently I’ve seen people try to dive into WebScript development without a concrete understanding of the foundational elements of the API. When I was set the task of organising an internal ‘hackathon’ as part of a ‘company day’ I decided that the goal should be to create a hands-on code-based tutorial.
I’m lifting the lid on my latest pet project which is set to revolutionise the ECM world. The codename is mu-fresco as it puts Alfresco into a Hadron collider with microservices.
This came about as I didn’t have access to 448 cores of JVM Azul goodness. The pretotype used 20 over-clocked Raspberry Pi units and an old HP Superdome picked up from eBay (I needed something beefy for the database and it was cheaper than RDS). After a bit of light surgery with a sharp scalpel, aka Spring Remoting with Hessian, it was time to awaken Frankenstein’s monster. The results are very promising though there are still a few kinks to be ironed out, with the Solr 1.4 index being one and the shared database schema between microservices being a glaring architectural impurity.
As for the next iteration, well “I’ve decided to take my work back underground to stop it falling into the wrong hands”.
At the start of a new year it’s always interesting to look back at the year that has just gone – arguably the most important event for content management in 2010 was the ratification of CMIS 1.0 in May.
Content Management Interoperability Services is an open standard to enable greater interoperability of Enterprise Content Management (ECM) systems and is built on top of other proven open web standards such as Atom and OpenSearch. Alfresco has been at the forefront of CMIS and Alfresco 3.3 provided full support for CMIS 1.0 (some of the earlier versions implemented drafts of the CMIS standard).
Note: this was the original draft for the article published on the Ixxus blog.