This document discusses the use of open source tools for entrepreneurship and software development. It begins by stating that the talk is intended for newcomers to open source, startups, and those interested in software projects or careers. It then provides background on the speaker and their experience before defining open source as promoting universal access and redistribution of designs. The document lists many popular open source databases, frameworks, servers and other tools that can be used for projects. It emphasizes asking the right questions about goals, users, and requirements before choosing tools. It also stresses system design, testing features with users, and ongoing maintenance like security, backups and monitoring.

1. Roles of Open Source in
Entrepreneurship in Development
wanleung - 2nd Dec 2013

2. This talk is for Who?
•
•
•
•
Newbie in the Open source world
Startups
For those who want to start a new software
project
For those who want to work in the software
development field.

3. This talk is for Who?
For those, Who think writing Software is just a
piece of cake,
something like just clicking a button,
a Facebook clone or Whatsapp clone will be
come out
in 60 seconds
=P
(joking)

4. About Me
● Vice-Chairman of the HKLUG
● Over 10 years experience on Linux
● Experience on Backend services, website,
web API development
● Experience on virtualization and Cloud Farm
building
● http://about.me/wanleung

5. About Me
● Co-founder of LinkOmnia
● http://www.linkomnia.com
● Providing services on Consultancy and
Customized Products
● Strengths on Cloud Computing and Big Data

6. What is Open source?
open source as a development model
promotes
a) universal access via free license to a
product's design or blueprint, and
b) universal redistribution of that design or
blueprint, including subsequent
improvements to it by anyone
From WIKI

7. Why use Open source?
● Free Licenses (MIT, Apache, LGPL...)
● Cost effective
● existing solutions / similar solutions - need
not to reinvent the wheel
● Have Rights to modify and fit into the
business models / the requirement of the
clients.
● Helps are all over the world

8. What can we use?
Database:
(SQL) PostgreSQL, MySQL...
(NoSQL) Redis, Cassandra, MongoDB...
(Graph DB) neo4j, Rexster…
•
•
•
File base:
SQLite, BDB...

9. What can we use?
Common Web / API Frameworks:
Dancer, Catalyst... (Perl)
Django, Grok, Pylons, TurboGears...
(Python)
Kohana, cakephp… (Php)
Revel, go-restful... (Go lang)
Ruby on Rails (Ruby)
mojito, blueprint (node.js)
•
•
•
•
•
•

10. What can we use?
•
•
•
•
•
•
Nginx, Apache, Tomcat (webserver, reverse
proxy)
haproxy, pound (reverse proxy)
squid (web proxy)
ImageMagick, GIMP, OpenCV...(Image
Processing)
RabbitMQ, ActiveMQ (Message Queue)
Postfix, exim (Mail Server), dovecot
(IMAP,POP3)

11. What can we use?
•
•
LibreOffice, KOffice, Abiwords,
Numeric(Office Tools)
VSFTPD, ProFTPD (FTP Server)
Bootstrap (CSS), jQuery (Javascript),
Prototype (Javascript)
And More, and more...

12. What can we use?
•
•
•
•
Google is your good friend
Github is your good friend
Forums are also your good friends
Join the local Open source communities
Please Don’t hesitate to ask questions
And
Please Don’t hesitate to answer questions

13. How to use them Right?
What is the aim of the project?
What is the scope of the project?
How many time or stages to commit?
How many users you want to support on each
stage?

14. How to use them Right?
Does the product need servers?
Does the servers need high-availability?
How important of the data?
How frequent of the data update?
How frequent of the data request?
How large of the data set?
What is the relations between each data?
How many dimensions?

15. How to use them Right?
Think about the behavior of the user.
How many request and update on the user on
each time using?
Does the user accept the down time?
How long?

16. How to use them Right?
The user has to see the update “Instantly”.
The other users also have to see the update
“Instantly”.
What is the meaning of
“Instantly/Now/Present”?
Does it accept delay?
What will happen if the user saw an Error
page or waiting for the request for a long

17. How to use them Right?
Those questions you have to ask yourself
before you start your project.
Software is not totally virtual, Software is also
limited by the physical hardwares.
Different Answers will affect the use of
technology, tools, design, UX,
Development Time & Cost.

18. How to use them Right?
Security is Important. Do it first. It is hard to
change afterward.
Hacking is everywhere.
Don’t think small site won’t get attack.
Beware SQL injection, API/CGI injection
Use the Right security method, especially in
Password store and Password Recovering.

19. How to use them Right?
System Design: Think Large
But execute in small scope first.
Large system = many components
= complicate
= Time
= Money

20. How to use them Right?
Think Large = Prepared how to scale up
Start in small scope = few components
= Less code
= Less bug
= easy to fix

21. How to use them Right?
Less is More
Get feedback from users and change much
easier.
Time == Money

22. How to use them Right?
Database is not just a Data bin.
A good data structure
= better organise
= better indexing
= better performance
= faster
Repacation == High availability
Backup == Data Recovery

23. How to use them Right?
Web server:
Concurrency User
Connection Pool
Proxy
Cache
Message Queue
Deployment tools
Monitoring tools

24. How to use them Right?
•
•
•
•
Google is your good friend
Github is your good friend
Forums are also your good friends
Join the local Open source communities
Please Don’t hesitate to ask questions
And
Please Don’t hesitate to answer questions

25. Q&A
Thanks.