Your SlideShare is downloading. ×
Web Content Management System Deployment Patterns
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Web Content Management System Deployment Patterns

2,876
views

Published on

My slides on Web Content Management System Deployment Patterns from the Gilbane Conference in San Francisco.

My slides on Web Content Management System Deployment Patterns from the Gilbane Conference in San Francisco.

Published in: News & Politics, Technology

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,876
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
58
Comments
0
Likes
1
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 on tent he re --> Web Content Deployment Patterns presented by Seth Gottlieb The Gilbane Conference San Francisco, CA June, 2009 10/09/2007 © Copyright 2009 Content Here. 1
  • 2. <!-- content here --> Patterns? 11/2/2008 © Copyright 2009 Content Here. 2
  • 3. <!-- content here --> Patterns? Re-usable solutions to recurring problems 11/2/2008 © Copyright 2009 Content Here. 2
  • 4. <!-- content here --> All WCM systems do it 11/2/2008 © Copyright 2009 Content Here. 3
  • 5. <!-- content here --> All WCM systems do it When? 11/2/2008 © Copyright 2009 Content Here. 3
  • 6. <!-- content here --> Key distinction FRY BAKE 11/2/2008 © Copyright 2009 Content Here. 4
  • 7. <!-- content here --> Different architectures Request Time Publish Time FRY BAKE != delivery publisher delivery repository repository management management 11/2/2008 © Copyright 2009 Content Here. 5
  • 8. <!-- content here --> Key distinction PULL PUSH 11/2/2008 © Copyright 2009 Content Here. 6
  • 9. <!-- content here --> Each has its advantages FRY BAKE Dynamism Performance/ Stability personalization availability high traffic access control cost savings “website in a box” decoupling immediacy 11/2/2008 © Copyright 2009 Content Here. 7
  • 10. <!-- content here --> The products have chosen FRY BAKE 11/2/2008 © Copyright 2009 Content Here. 8
  • 11. <!-- content here --> The products have chosen FRY BAKE 11/2/2008 © Copyright 2009 Content Here. 8
  • 12. <!-- content here --> Each can compensate FRY BAKE Dynamism Performance/ Stability caching code publishing clustering fragment publishing structured publishing dynamic client 11/2/2008 © Copyright 2009 Content Here. 9
  • 13. <!-- content here --> 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. 11/2/2008 © Copyright 2009 Content Here. 10
  • 14. <!-- content here --> 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 11/2/2008 © Copyright 2009 Content Here. 11
  • 15. <!-- content here --> 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 11/2/2008 © Copyright 2009 Content Here. 12
  • 16. <!-- content here --> 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 11/2/2008 © Copyright 2009 Content Here. 13
  • 17. <!-- content here --> Key challenges >> Baking systems .. constant publishing .. extensive interlinking .. user generated content >> Frying systems .. distributed delivery data centers .. highly variable traffic 11/2/2008 © Copyright 2009 Content Here. 14
  • 18. <!-- content here --> Thank You Seth Gottlieb Content Here seth@contenthere.net http://www.contenthere.net 11/2/2008 © Copyright 2009 Content Here. 15

×