Basic architecuture and operation concept of Backlog and Cacoo

Basic architecuture and operation concept of
and
2013.05.09(thr) Takashi SOMEDA

Takashi SOMEDA
AWS User Group Singapore 1st Meetup
http://twitter.com/tksmd
Nulab, Inc.
Technology Evangelist
JAWS UG Kyoto Branch leader
About me
http://facebook.com/takashi.someda

My favorite
http://en.clouddesignpattern.org/index.php/Main_Page
About CDP
AWS Service CDP

My career
Sun Microsystems
(acquired by Oracle)
Benchmark Engineer
Exploratory IT Human Resources Project
( MITOH Program )
Freelance Engineer
Synergy Marketing, Inc.
Technology Researcher
Choistudio, Inc.
CTO
Nulab, Inc.
Engineer / Evangelist
2002
2005
2006
2008
2010

Backlog is a project management tool used by 145,000 users mainly in Japan.
In addition to issue management feature, Backlog provides
• File sharing by WebDAV
• Git and Subversion repository hosting.
2 years ago, we increased available capacity up to 30 times while the price was
not raised.

840,000 users around the world draw wireframes, network diagrams,
business plans etc on Cacoo.
Cacoo provides basic functionality as a draw tool and powerful collaborative
features like
• Simultaneous Editing on same diagram by multiple users
• Tightly integration with Google+ Hangouts that enables users to edit
diagrams while Video chatting.

Nulab & AWS
Oct. 2010
Cacoo launched Sep. 2010
Started migrating Backlog to AWS
Apr. 2011
Renewal of plan
( completely migrated )
Nov. 2011
backlogtool.com launched
Apr. 2012
Cacoo for Google+ Hangouts started
We’re now developing brand new service !
It will be unveiled on Summer 2013.
Please follow us on twitter @nulabinc.

Ops Team
2010/10 2011/10 2012/10 2013/05
Backlog :38,000users
Cacoo:62,000users
Cacoo:200,000users
Cacoo:600,000users
Cacoo:840,000users

Agenda
Basic Architecture
Action First
Automation
Monitoring
Design for failure
Summary

Basic Architecture
http://www.flickr.com/photos/83633410@N07/7658034524/in/photostream/

Backlog

Cacoo

AWS services we use

Do you have an experience to
operate a service stored data
size of which is
1〜2TB.

We love RDBMS

Running on LVM
RAID0
Striping

Working with partition

Keep Simple
Be careful which AWS services to use.
Don‟t choose No-SQL storage
just because you want to be a cloud guy.
Data store you selected affects
both development and operation process.

Action First

Value first
Don‟t prepare too much for uncertain future.
Infrastructure CAN be fit to a service afterward.
The most important thing is to deliver “value” to users.

Automation
http://www.flickr.com/photos/nicmcphee/2558167768/

fabric
@task
@roles(„app‟)
def all_release():
sudo(“service tomcat stop”)
put(“new.war”,”/tmp/new.war”)
run(“cp –p /tmp/new.war /webapps/ROOT.war”)
sudo(“service tomcat start”)
@task
@hosts(„web01‟,‟web02‟,‟mail01‟,‟mail02‟)
def fluent_agent_reload():
sudo("/etc/init.d/fluent-agent-lite reload")
http://fabfile.org/
# install by pip
$ pip install Fabric
# execute task
$ fab app.all_release

cuisine
def install():
if file_exists('/usr/local/fluent-agent-lite/bin/fluent-agent-lite'):
return
with mode_sudo():
with cd('/usr/local/src'):
run('wget https://github.com/downloads/tagomoris/fluent-agent-lite/fluent-
agent-lite.v0.6.tar.gz')
run('tar zxvf fluent-agent-lite.v0.6.tar.gz')
with cd ('fluent-agent-lite'):
run('./bin/install.sh‟)
https://github.com/sebastien/cuisine

fabric/cuisine
With boto ( python SDK ), you can do various operations.
cuisine helps you to build environment like chef.
Simple! Simple! Simple!

Staging & Deploy

Automation! Automation!
For everyone to be able to operate easily.
Automation itself is NOT a goal.

Monitoring

Monitoring Stack

Daily Monitoring

Log mangement

Monitoring
Add monitoring point to detect failure in the future.
Tools call us when they find something wrong.
Keep monitoring working well.

Design for failure
http://www.flickr.com/photos/83633410@N07/7658236076/sizes/l/in/photostream/

Multiple AZ

Multiple AZ
You should monitor network connectivity between the instances on
other AZ.
Fortunately, we have not experienced AZ failure yet.
We don‟t experience network latency between AZ so far.

Multi tenancy

Multi tenancy
It is quite well that the impact of failure is limited.
You might need extra-effort to integrate other services.
For business or personal use

If service failure happen
Your website should be running on other AZ/region than production
environment.

Summary
http://www.flickr.com/photos/nauright/2662160957/

Design Basics
We focus on
NOT decreasing failures
BUT building process
to recover quickly
after failure happens.

What AWS brings to us ?!
Flexibility that enables us to change
infrastructure quite easily
corresponding to service growth
afterward.

What AWS brings to us ?!
Giving huge power that enables
even a small team to provide
a service used around the world.

Thanks!!
Any Questions ?!

Basic architecuture and operation concept of Backlog and Cacoo

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Basic architecuture and operation concept of Backlog and Cacoo

Similaire à Basic architecuture and operation concept of Backlog and Cacoo (20)

Plus de Takashi Someda

Plus de Takashi Someda (13)

Dernier

Dernier (20)

Basic architecuture and operation concept of Backlog and Cacoo