WHEN ARCHITECTURE AND OPEN SOURCE COLLIDE

562
-1

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
562
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

WHEN ARCHITECTURE AND OPEN SOURCE COLLIDE

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

×