30
javier ramirez @supercoco9 Why and how we built teowaki.com two developers journey into the dark side of software techcity talks

Why and how we built teowaki

Embed Size (px)

DESCRIPTION

Two developers journey into the dark side of technology. Talk delivered for Code Collective and It @ ñ UK as part of the techcity talks initiative

Citation preview

Page 1: Why and how we built teowaki

javier ramirez@supercoco9

Why and how webuilt teowaki.com

two developers journey intothe dark side of software

techcity talks

Page 2: Why and how we built teowaki
Page 3: Why and how we built teowaki
Page 4: Why and how we built teowaki
Page 5: Why and how we built teowaki
Page 6: Why and how we built teowaki
Page 7: Why and how we built teowaki
Page 8: Why and how we built teowaki
Page 9: Why and how we built teowaki
Page 10: Why and how we built teowaki
Page 11: Why and how we built teowaki
Page 12: Why and how we built teowaki

RecurringRevenue:

I need a product

Page 13: Why and how we built teowaki

the product on the side

Page 14: Why and how we built teowaki
Page 15: Why and how we built teowaki

Your idea is not so valuable

Page 16: Why and how we built teowaki

Your team is

Page 17: Why and how we built teowaki
Page 18: Why and how we built teowaki
Page 19: Why and how we built teowaki

broken!

Page 20: Why and how we built teowaki

https://teowaki.com@teowaki

Page 21: Why and how we built teowaki
Page 22: Why and how we built teowaki

set up in the UK is just £15*

* don't need to do it until you start operating

Page 23: Why and how we built teowaki

External services we pay for:wordpress £0.70AWS, google, Maxmind GeoIP < £1ICO £3pivotal tracker £3.75Domain and SSL wildcard certificate £10flexible co-working space £30digital ocean £34

free services: trello,new relic,pingdom,rollbar, google Apps, google Analytics

Page 24: Why and how we built teowaki

£83 per month*

* zero costs in software licenses

Page 25: Why and how we built teowaki

Salaries* are the largest expense* try to hire part-time at first

Page 26: Why and how we built teowaki
Page 27: Why and how we built teowaki
Page 28: Why and how we built teowaki

Hypermedia RESTful API (Ruby on Rails)

Kind-of-responsive web application (AngularJS)

Background jobs queue (Redis)

Background workers (Ruby on Rails)

Postgresql master/slave, for text search too

Redis master/slave (with LUA scripting)

Memcached

Page 29: Why and how we built teowaki

Devops

Ansible for provisioning

Monit and Munin for server health check

Google Bigquery for bigdata processing

S3 and Glacier for backups (every minute for postgresql, every hour for Redis and stats)

Page 30: Why and how we built teowaki

Cheers!

If you love your developers, please tell them about

https://teowaki.com

javier [email protected]

techcity talks