WHEN ARCHITECTURE AND OPEN SOURCE COLLIDE
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

WHEN ARCHITECTURE AND OPEN SOURCE COLLIDE

on

  • 658 views

 

Statistics

Views

Total Views
658
Views on SlideShare
658
Embed Views
0

Actions

Likes
0
Downloads
7
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

WHEN ARCHITECTURE AND OPEN SOURCE COLLIDE Presentation Transcript

  • 1. WHEN ARCHITECTURE AND OPEN SOURCE COLLIDE
  • 2. !AGENDA
    • Religious debate
    • Bashing of proprietary software company
    • Deep dive in to a particular open source project
    • Open source hardware
  • 3. AGENDA
    • Definition, Licensing  & players
    • Open source based architecture examples
    • Best practices
    • ROI, TCO and other TLA
    • Open source tools for architecture
    • Want to be an open source developer?
    • Future FOSS trends
    You get to pick the agenda!
  • 4. WHAT IS OPEN SOURCE
    • The freedom to run the program, for any purpose
    • The freedom to study how the program works, and adapt it to your needs
    • The freedom to redistribute copies
    • The freedom to improve the program, and release your improvements to the public.
  • 5. FREE SPEECH NOT FREE BEER
  • 6. OPEN SOURCE LICENCES
    • Copyleft – anyone can reproduce, adapt or distribute the work as long as any resulting copies are also bound by the same copyleft licensing scheme.
    • Non-copylefted - copies or modified versions may not be free at all. Anyone can distribute the software as a proprietary software product or under another FOSS license.
    • Public domain – no copyright is imposed, anyone can do anything with the work.
  • 7. KEY PLAYERS
    • Open source community
      • SourceForge + 1,000,000,000 other sites
    • Open source companies
      • Jboss/Red Hat
      • SugerCRM
    • Proprietary software vendors (with an open source angle)
      • Microsoft
      • Sun
      • IBM
  • 8. WHERE TO NOW?
    • Open source based architecture examples
    • Best practices
    • ROI, TCO and other TLA
    • Open source tools for architecture
    • Want to be an open source developer?
    • Future FOSS trends
  • 9. EXAMPLE OPEN SOURCE ARCH PHP Apache MySQL Linux
  • 10. EXAMPLE OPEN SOURCE ARCH Java JBoss / Glassfish PostgreSQL Linux Mule / ServiceMix
  • 11. OPEN SOURCE ARCHITECTURAL COMPONENTS
    • Microsoft enterprise libraries and application blocks – by patterns and practices group
    • Moonlight / MONO - open source implementation of .NET and RIA
    • Client side software – like Firefox and Open Office and OS
    • Mobile software – Android, J2ME
    • IDE – NetBeans, Eclipse
  • 12. WHERE TO NOW?
    • Open source based architecture examples
    • Best practices
    • ROI, TCO and other TLA
    • Open source tools for architecture
    • Want to be an open source developer?
    • Future FOSS trends
  • 13. BEST PRACTICES – CHOOSING
    • Projects with strong community support
    • Company backed-up projects
    • Supporting standards
    • Low learning curve
    • Easy integration
    • Documentation
    • Same licence stack & Non copyleft (IMHO)
    • See ROI, TCO and other TLA for more information
  • 14. BEST PRACTICES – DEVELOPING
    • Latest is greatest Vs. stable is greatest
    • Use API rather then hack the code
    • Patch back to the community
    • Keep a backup of source of the project in house
  • 15. WHERE TO NOW?
    • Open source based architecture examples
    • Best practices
    • ROI, TCO and other TLA
    • Open source tools for architecture
    • Want to be an open source developer?
    • Future FOSS trends
  • 16. RETURN ON INVESTMENT
    • ROI – Return On Investment
    • Gain from investment can be measured in a post-implementation process – fit for purpose, easy to use, business value, adoption.
    • Cost of licences can be marginal in cost of investment .
  • 17. TOTAL COST OF OWNERSHIP
    • TCO – Total Cost of Ownership
  • 18. TOTAL COST OF OWNERSHIP
    • example 1: Custom application
    Web DB integration
    • Low percentage of licensing cost
    • High cost of development and testing
    • High risk averse project
    • No single open source project that is fit for purpose
    • Current investment in non-FOSS
    Proprietary software has lower TCO
  • 19. TOTAL COST OF OWNERSHIP
    • TCO – example 2: Simple CMS project
    CMS
    • Low percentage of development cost
    • Long lifespan drives licence and support cost
    • A single open source project that fits the purpose
    • ‘ no’ to ‘simple’ integration with current investment
    Open source has lower TCO
  • 20. OTHER THINGS TO CONSIDER RE COST
    • Current infrastructure/software investment
    • Learning curve and expertise of the dev team
    • Organisational politics
    • The desktop angle
  • 21. ROI, TCO AND OTHER TLA
    • Other acronyms to think about:
      • SLA – Service Level Agreement
      • SEP – Someone Else’s Problem
      • TTM– Time To Market
  • 22. WHERE TO NOW?
    • Open source based architecture examples
    • Best practices
    • ROI, TCO and other TLA
    • Open source tools for architecture
    • Want to be an open source developer?
    • Future FOSS trends
  • 23. OPEN SOURCE TOOLS FOR ARCHITECTURE
    • Protégé - a free, open source ontology editor and knowledge-base framework.
  • 24. OPEN SOURCE TOOLS FOR ARCHITECTURE
    • BOUML is a free UML 2 tool box allowing you to specify and generate code in C++, Java, Idl, Php and Python.
  • 25. OPEN SOURCE TOOLS FOR ARCHITECTURE
    • Eclipse MDT - Model Development Tools
  • 26. WHERE TO NOW?
    • Open source based architecture examples
    • Best practices
    • ROI, TCO and other TLA
    • Open source tools for architecture
    • Want to be an open source developer?
    • Future FOSS trends
  • 27. SO YOU WANNA BE A FOSS DEVELOPER?
    • Use SourceForge or Codeplex to host your project
    • Use freshmeat or /. to publicizes your project
    • Focus of fast delivery and transparency
    • Be mindful of code contributions
    • Integrate with other projects and get them to link to you
  • 28. OPEN SOURCE REVENUE MODELS
    • Dual license model
    • Release the product under a restrictive open-source license and provide an alternative proprietary license.
    • Motivation : The client really likes the open-source product and needs it for commercial use. He does not want to breach the open-source license and is willing to pay for a proprietary license.
    • Open-source license : GPL is the only suitable license to this strategy because of its restrictive constraints and its viral behavior (you need to be GPL to use GPL).
    • Example : MySQL
  • 29. OPEN SOURCE REVENUE MODELS
    • Dual product model
    • Penetrate the market by releasing an open-source product, sell a different product (extended version, plug-ins or an application that is based on the open-source product).
    • Motivation : The user gets to be a part of an open-source community process, contributes to the source and improves it. Users purchase other related products from the project professionals.
    • Open-source license : MIT, BSD, Apache or any other non-copyleft license.
    • Example : eclipse and its non open source plug-ins.
  • 30. OPEN SOURCE REVENUE MODELS
    • Professional services model
    • Sell support/customization and other Professional services.
    • Motivation : We are the experts in this open-source project because we wrote it, therefore clients would like to purchase support and other services from us.
    • Open-source license : Any
    • Example : JBoss
  • 31. WHERE TO NOW?
    • Open source based architecture examples
    • Best practices
    • ROI, TCO and other TLA
    • Open source tools for architecture
    • Want to be an open source developer?
    • Future FOSS trends
  • 32. FUTURE TRENDS
    • A good open source productivity suite is still not there yet (more a wish list then a trend)
    • Market condition is pushing open source to the client and enterprise
    • Software as a service is taking the free beer out of open source – checkout AGPL
  • 33. WHERE TO NOW?
    • Open source based architecture examples
    • Best practices
    • ROI, TCO and other TLA
    • Open source tools for architecture
    • Want to be an open source developer?
    • Future FOSS trends
  • 34. THANKS
    • Amir Shevat
    • Email: [email_address]
    • Blog: http://spacebug.com