Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Drupal in the Enterprise, IBM and Norwegian Cruise Line
Similar to Drupal in the Enterprise, IBM and Norwegian Cruise Line (20)
Recently uploaded
Recently uploaded (20)
Drupal in the Enterprise, IBM and Norwegian Cruise Line
- 1. Drupal in the Enterprise IBM and Norwegian Cruise Line Rob Shea
- 7. NCL.com
- 15. flickr.com/photos/79117087@N00/1716249985/ OSS Licensing
- 18. Support
- 20. OSS Support
- 22. Content Model
- 23. Business Needs Integration Legacy Data Template Needs
- 26. Integration
- 30. Large development teams flickr.com/photos/33948692@N00/539413957/
- 32. Infrastructure
- 33. Infrastructure
- 34. Caching Strategy
- 37. Code Deployment
- 39. Monitoring
- 41. Agile Practices
- 43. What did you think? Locate this session on the DCC website: http://chicago2011.drupal.org/sessions Click the “Take the Survey” link. Thanks!
Editor's Notes
- Working on NCL from pre-production, thru development thru support Number of differences between Drupal in the Enterprise “ Conventional” Drupal implementations
- IBM known for BIG IRON
- And big challenges
- IBM Interactive, a digital agency within IBM Not just developing solutions with IBM software, such as WebSphere Portal Use open source, such as Drupal and Ruby, mobile apps
- NCL 3rd largest cruise line 11 cruise ships
- 8% estimated market share worldwide $2.25b estimated 2011 revenue
- NCL.com Revenue generating – booking cruises and excursions, making reservations High availability High performance 4m visitors/month 32m page views/month Higher waves of traffic during promotions
- From mid-west Wife thinks I spend my time in Miami doing this.
- Kids this
- Friends this
- More like this
- And sometimes like this
- Used by the enterprise for decades Enterprise purchases software license from vendor. Enterprise perspective: Legal ownership of code is well-defined. Software backed by established entity.
- OSS Licensing - Software distributed under open source (GPL) license. Enterprise perspective: Who “owns” the license? Who “owns” the code? Who backs the software? Community Who is the community???
- Conversations like this result from differing perspectives even within the IBM Team.
- Support must be addressed before project, not after. Support is critical in the enterprise. While people may come and go, support needs to remain consistent.
- Enterprise purchases support contract from vendor. (maybe same as license) Enterprise engages IT (internal or contract) for regular maintenance. Enterprise engages support vendor for escalated support. Enterprise perspective: Well defined escalation procedures Accountability
- Great for developers Google.com Drupal.org IRC Enterprise perspective: No accountability No escalation path
- Content model critical many content types many integration points
- Inputs to content model
- Process driven by documentation in enterprise Interview content owners Document content model Define content types Export legacy content Import legacy content Tweak content types repeatedly to address changing import and template needs
- Legacy CMS – One time import, daily import via cron Endeca Search Index – XML from Drupal on demand + cache data = index JSON back to Drupal Geotargeting – IP address on demand Flash XML content nodeapi Many potential points of failure Many drivers of content model
- Many challenges
- Staging – Full preview with Drupal, Flash and Endeca Deploy module Not widely used No upgrade path to D7 D8?
- Pre-production – small team Build – large team Maintenance – small team
- Lack of team lead can result in diff modules being used for same tasks.
- Sample infrastructure Potential issues Load balancing – HTTP headers Intrusion detection - DOS Firewall - load
- Cache everywhere Drupal caching – 30 minutes to 3 hours
- Monitoring is critical quickly identify issues track issues to their source Don’t depend on infrastructure team
- Agile isn’t faster. Agile is faster.