Open source at Wongnai Codemania IIO

Me ● Manatsawin Hanmongkolchai ● Junior Architect at Wongnai ● Follow me on Medium at life.wongnai.com and blog.whs.in.th

Today's agenda ● Open source and Wongnai Infrastructure ● Open source @ Wongnai

Where is Wongnai ● We operate 126 vCPU (dynamically scaled) on Amazon EC2/RDS for production and development (incl. partner) use ● 20 vCPU on Google Compute Engine for development use ● All are in Singapore region

Avoiding cloud lock-in ● Suppose tomorrow Amazon announce that it will raises the price by 40% ● Avoiding cloud lock-in means we could move to Google Cloud (or any other) easily ● Even better if coupled with hybrid cloud solution

Avoiding cloud lock-in ● We have a policy not to use cloud services that is not replacable or disabled in our core systems ○ RDS: Replaced by instance on GCE ○ Elasticache: Replaced by instance on GCE ○ X-Ray: Disabled on GCP ○ Kubernetes Engine: Replaced by Kops

Avoiding cloud lock-in ● Use open source software alternatives for critical services: ○ ECS -> Kubernetes ○ SQS -> RabbitMQ

Avoiding cloud lock-in ● But sometimes it can be very expensive to build your own, so using cloud services is better ○ S3: Replacable, but instance disk space is more expensive ○ Load balancer: Replacable by instances ○ SES: Replacable by mail server, but poor deliverability

Avoiding cloud lock-in Pros ● Migrate between cloud providers easily when needed ● Resistant to hostile changes from cloud provider ● More visibility Cons ● Need to manually manage service ● Can be more expensive

Today's agenda ● Open source and Wongnai Infrastructure ● Open source @ Wongnai

Open source @ Wongnai ● Come visit us at github.com/wongnai

What we do ● Our most popular project: kube-slack ● Thumbor-text-filter, key of our new Chatbot experience ● Patches to softwares we use ● We're working on putting our internal tools out there

Why open sourcing? ● Why not? It's not your core business anyway ● Free improvements and testing (bug reports)

Why open sourcing? When you open source useful code, you attract talent. Every time a talented developer cracks open the code to one of your projects, you win. Tom Preston-Werner GitHub Co-founder

"But my code is bad!"

Improve your code quality ● When writing any code, always think that it will be open sourced ○ Don't couple it with internal infrastructure/components that you don't intend to open source ○ Produce maintainable code

Improve your code quality ● Contributing patches to projects help you improve yourself ○ Learn from maintainer's code review ○ Study unfamiliar, large scale codebase ○ Get to know the inner working of your system

Side story: my first PR ● My first PR was to Symfony/Process (PHP library) back in 2014 ● A simple three lines duck typing fix for reading zero

Side story: my first PR ● Turned out to be more than three lines...

Side story: my first PR ● Testing is not so easy either..

Going open source ● Don't workaround library bugs, fix it upstream.

Signing CLA Many projects require a CLA to be signed CLA assigns the copyright of your contribution to the host organization.

Going open source ● Adopting new tech could lead to potential project ideas

Summary ● Open source infrastructure keep vendor lock-in away ● Build your company's resume with open source ● Giving back make a healthy open source community

Thank you