• Like
WCM Deployment Patterns
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

WCM Deployment Patterns

  • 1,049 views
Published

This presentation shows the different categories of CMS (baking and frying) and how they can be deployed. For a narrative,

This presentation shows the different categories of CMS (baking and frying) and how they can be deployed. For a narrative,

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
1,049
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
25
Comments
1
Likes
3

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. <C O N T E N T H E R E/> Web Content Deployment Patterns presented by Seth Gottlieb jboye08 aarhus, dk november, 2008 10/09/2007 © Copyright 2007 Content Here. 1
  • 2. < C O N T E N T H E R E /> Patterns? Re-usable solutions to recurring problems 10/09/2007 © Copyright 2008 Content Here. 2
  • 3. < C O N T E N T H E R E /> Why do we need patterns? 10/09/2007 © Copyright 2008 Content Here. 3
  • 4. < C O N T E N T H E R E /> Why do we need patterns? 10/09/2007 © Copyright 2008 Content Here. 4
  • 5. < C O N T E N T H E R E /> Why do we need patterns? customers vendors 10/09/2007 © Copyright 2008 Content Here. 5
  • 6. < C O N T E N T H E R E /> Patterns give us a common language to describe repeatable solutions >> Architectural Patterns .. Similar solutions to the same problem >> Usage patterns .. Universal usage scenarios >> Implementation patterns .. PSO Experience (formal/informal) .. Productized solutions 10/09/2007 © Copyright 2008 Content Here. 6
  • 7. < C O N T E N T H E R E /> Where it all started >> Fried >> Baked 10/09/2007 © Copyright 2008 Content Here. 7
  • 8. < C O N T E N T H E R E /> A problem that all WCM systems face When? 10/09/2007 © Copyright 2008 Content Here. 8
  • 9. < C O N T E N T H E R E /> Different architectures Request Time Publish Time != delivery publisher delivery repository repository management management 10/09/2007 © Copyright 2008 Content Here. 9
  • 10. < C O N T E N T H E R E /> Each has its advantages Dynamism Performance/ Stability personalization availability high traffic access control cost savings “website in a box” decoupling 10/09/2007 © Copyright 2008 Content Here. 10
  • 11. < C O N T E N T H E R E /> Most products are based on one of the strategies 10/09/2007 © Copyright 2008 Content Here. 11
  • 12. < C O N T E N T H E R E /> Each has compensation strategies Dynamism Performance/ Stability caching code publishing clustering fragment publishing structured publishing dynamic client 10/09/2007 © Copyright 2008 Content Here. 12
  • 13. < C O N T E N T H E R E /> Frying Systems: reusing outputs 10/09/2007 © Copyright 2008 Content Here. 13
  • 14. < C O N T E N T H E R E /> Caching strategies >> Data caching .. Read-optimized repository .. Object caching >> Page caching .. Fragment caching .. Full page caching OSCache .. Reverse proxy >> Site caching .. Spider .. Static deploy GNU WGet CMFDeployment 10/09/2007 © Copyright 2008 Content Here. 14
  • 15. < C O N T E N T H E R E /> Caching: The Whole Hog reverse proxy load balancer pages fragment renderer cache object object satellite satellite cache cache repository repository satellite central repository repository 10/09/2007 © Copyright 2008 Content Here. 15
  • 16. < C O N T E N T H E R E /> Baking style: Adding logic 10/09/2007 © Copyright 2008 Content Here. 16
  • 17. < C O N T E N T H E R E /> Code publishing (parbaked) >>Strategy: Use the CMS to publish unexecuted scripting code to an active delivery tier >>Advantages .. Good for small touches of dynamism with “Model 1” architectures .. Choose your own scripting language >>Disadvantages: .. Breaks “MVC” because model is baked into the view .. Deployment issues on Java. Better for .NET and PHP based delivery tiers. 10/09/2007 © Copyright 2008 Content Here. 17
  • 18. < C O N T E N T H E R E /> Dynamic client >> Strategy: Statically publish content and use Javascript on the client to add dynamism >> Advantages .. Minimal disruption to static publishing system .. Lightweight integration across multiple systems >> Disadvantages: .. Security can be a problem .. SEO issues .. Accessibility issues .. Browser compatibility 10/09/2007 © Copyright 2008 Content Here. 18
  • 19. < C O N T E N T H E R E /> Fragment publishing >> Strategy: Use the CMS to publish HTML fragments that can be assembled by a dynamic web application >> Advantages .. Good for static blocks like headers, footers, and “about pages” .. Works well with portals >> Disadvantages: .. Preview issues .. Fragments are static .. Access control issues 10/09/2007 © Copyright 2008 Content Here. 19
  • 20. < C O N T E N T H E R E /> Structured publishing >> Strategy: Use the CMS to publish structured content into a dynamic web application >> Advantages .. Maximum flexibility on the delivery tier .. Maximum de-coupling: “Separation of Concerns.” >> Disadvantages: .. Need to have a data driven delivery tier .. Preview is often problematic 10/09/2007 © Copyright 2008 Content Here. 20
  • 21. < C O N T E N T H E R E /> Summary >> Different CMS architectures come with native strengths and weaknesses >> With patterns, you can transform your CMS .. Feed your content into a dynamic presentation layer .. “Re-heat” your pre-fried content 10/09/2007 © Copyright 2008 Content Here. 21
  • 22. < C O N T E N T H E R E /> Thank You Seth Gottlieb Content Here seth@contenthere.net http://www.contenthere.net http://blog.contenthere.net 10/09/2007 © Copyright 2008 Content Here. 22