Open Source & the Web

Talk about embracing open source. Given at a local enterprise technology conference.

Transcript

1. Open Source & the Web by David Rice ( davidjrice.co.uk )
2. How many of you have ever used open source software
3. How many of you have ever used the internet
4. How many of you still think you haven’t used open source software
5. answer: everyone who uses the internet, uses open source software
6. http://news.netcraft.com/archives/2010/03/17/march_2010_web_server_survey.html 7% 1% 7% 7% 24% 54% Web Server Market Share by Server Apache Microsoft Google Nginx lighttpd Other
7. http://news.netcraft.com/archives/2010/03/17/march_2010_web_server_survey.html 31% 62% 7% Web Server Market Share by License Other Open Source Proprietary
8. The Open Source Web Stack
9. Client Side Web Server App Server Application Database Operating System (HTML/CSS/JS) Nginx Passenger (Ruby on Rails / Ruby) MySQL Debian
10. Proprietary Web stacks have similar roles of component but are closed source
11. Why is proprietary information bad for us
12. Throughout human history there are positive examples of standardisation, knowledge sharing and open source
13. Modern Language Metric System Modern Medicine
14. However, for each positive example in history, there is also a negative where information was withheld to improve competitive advantage
15. In my opinion ideally all knowledge should be free, but that’s slightly optimistic for now...
16. How can we embrace open source today... and not be evil
17. If you need to retain some of your competitive advantage (a lot of companies still do)
18. Application Business Logic Design (HTML/CSS) Framework Libraries Application
19. Build Applications using open source plugins and libraries
20. Contribute improvements back to the community
21. Receive status, feedback & contributions from the community
22. Release new interesting libraries to the public
23. If you’re hiring, you have access to a pool of smart people already experienced with your technology
24. An incentive for existing employees/contractors, their work will be made public
25. As we tend towards more reusable standardised libraries
26. We have do deal with less bespoke code... faster time to market, lower costs
27. The “glue” becomes secondary, and we end up with a more maintainable solution...
28. ...that adheres to open source standards and can be maintained by anyone
29. we end up with configurations and ordering of lots of small reusable building blocks
30. that can be developed in an agile and iterative way, organic like DNA
31. Now, what about even more forward thinking... be good
32. There’s also another breed of company, giving everything away open source
33. They’re driving profit through expert services & support around the open source software
34. RedHat couch.io
35. A few examples
36. Active Merchant (Realex) A payment gateway abstraction library http://github.com/davidjrice/active_merchant
37. Open Translink A Work in Progress collection of demos using Translink’s data set http://translink.davidjrice.co.uk http://github.com/davidjrice/translink
38. ATCO A Ruby library for parsing ATCO-CIF UK public transport data http://github.com/davidjrice/atco
39. node-comment Real Time Streaming web chat demo using frontend & server side Javascript Node.js / CouchDB http://github.com/davidjrice/node-comment
40. Thanks, any questions me@davidjrice.co.uk @davidjrice github.com/davidjrice