Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante Speaker/Palestrante

Continuous Delivery through server side mash-ups

There's a typical problem facing the enterprise world. There is a well entrenched CMS system (like Alfresco, Teamsite, etc) and an enthusiastic agile team.

These commercial off the shelf(COTS) products were never designed for Agile development teams and the principles of continuous integration (CI) and delivery.

So how do you setup an automated integration and delivery pipeline doing trunk based deployments into Production of your enterprise quality CMS system and its content?

At ThoughtWorks we've encountered these problems in the field several times, and one approach has proved very effective.

This talk is about leveraging Ruby, Rails, and a couple of custom gems to implement a server side mash-up as a mechanism for CI and continuous delivery.

I'll cover architecture principles and patterns inherited from Sitemesh, Segmented content freshness, the decorator pattern, and HTTP based caching.

Speaker - Nigel Fernandes

Twitter

Nigel is a senior consultant and asylum inmate at ThoughtWorks Australia.

In the last five years he has worked across the UK, Germany, Australia and India with start-ups, global telecommunication leaders, e-commerce giants and even high profile government agencies.

He received Ruby enlightenment in 2006 and after years in Java and .Net wastelands, he's decided to atone for his past. His focus for the last few years has been introducing Ruby into traditional enterprise Java stacks.

 


sponsors

globo.com paypal caelum dextra gonow

support