Using Google Cloud Infrastructure for twindly (talk at Google DevFest Berlin 2014). Google Compute Engine, App Engine, Node.Js, OrientDB, Neo4J

1. Google Cloud Infrastructure
for
twindly
ASTRID PARAMITA MOCHTARRAM
I. ABIYASA SUHARDI
Saturday, November 22, 14

2. BEFORE WE START
Saturday, November 22, 14

3. WHO ARE YOU?
WHY ARE YOU HERE?
Saturday, November 22, 14

4. THE DREAM
Saturday, November 22, 14

5. twindly is a web application
for beauty geeks
to find their beauty twins and
discover products and looks
Saturday, November 22, 14

6. FINDING YOUR BEAUTY TWINS
Photography by Gianni Cumbo
(http://www.flickr.com/photos/gianni_cumbo)
Saturday, November 22, 14

7. SOCIAL:connects geek to geek
Saturday, November 22, 14

8. geek to products
Saturday, November 22, 14

9. RECOMMENDATION
Saturday, November 22, 14

10. WHICH ONE SUITS YOU BEST?
Saturday, November 22, 14

11. WHO ARE WE?
Saturday, November 22, 14

12. ASTRID
Founder + Dev 1
ABI
Co-Founder + Dev 2
Saturday, November 22, 14

13. Saturday, November 22, 14

14. TAKING OFF
Saturday, November 22, 14

15. PRE-CLOUD
Saturday, November 22, 14

16. Pre-Cloud > LAMP Stack
Saturday, November 22, 14

17. Pre-Cloud > LAMP Stack
(Hopefully) quicker to prototype
Familiar stack - LAMP (+)
Saturday, November 22, 14

18. Pre-Cloud > LAMP Stack
Recommendation implementation
Problems in scaling (-)
Saturday, November 22, 14

19. Maybe Node.JS?
• (+) Comfortable in node.js
• (-) HeroKu didn’t support Asian region
Saturday, November 22, 14

20. GOOGLE CLOUD
Saturday, November 22, 14

21. NO DEVOPS NO PROBLEM?
Saturday, November 22, 14

22. Google AppEngine
• App Engine (Platform as a Service)
• Supports Java, PHP, Python, Go
• Go !!
Saturday, November 22, 14

23. AppEngine + Go
• Backend: AppEngine, Go, BeeGo
• Frontend: AngularJS
• Build tools: Grunt, LESS, Twitter Bootstrap
• Database: Google Datastore
Saturday, November 22, 14

24. Saturday, November 22, 14

25. Google Startup Package
• For Small Startups
• $20K credits for 1 year for Google Cloud Platform
• Exploring Google Compute Engine
Saturday, November 22, 14

26. Google Compute Engine + Node.JS
• Go is really nice but we're more productive in Node.js
• Full stack development using JavaScript, sharing codes between server,
frontend client, and build tools.
• More libraries (web server, database drivers, frontend)
Saturday, November 22, 14

27. Google Compute Engine + Node.JS
• (+) More control: install anything, click-to-deploy
• (-) Setting up things manually: scaling, firewall, deployment
• Back then, we didn’t have Managed VM
Saturday, November 22, 14

28. Current stack
• Backend: Google Compute Engine, Node.js, KrakenJS
• Frontend: Backbone, Marionette
• Build tools: Grunt, LESS, Twitter Bootstrap, Browserify
• Google Datastore and Google Cloud Storage
• GraphDB through Google Compute Engine
Saturday, November 22, 14

29. Saturday, November 22, 14

30. RECOMMENDATION
Saturday, November 22, 14

31. Recommendation ≈ Big Data?
Saturday, November 22, 14

32. •Google BigQuery: not suitable for twindly’s use case
•Google Prediction API: maybe suitable, for later date
•Apache Mahout: maybe suitable, for later date
Saturday, November 22, 14

33. Saturday, November 22, 14

34. SQL
NoSQL
GraphDB
+ Gremlin
Saturday, November 22, 14

35. GraphDB : OrientDB | Neo4j
•Limited available library
•Back to node.js
•OrientDB + Docker on Google Compute Engine
Saturday, November 22, 14

36. CURRENT TWINDLY STACK
Saturday, November 22, 14

37. Saturday, November 22, 14

38. WHAT’S NEXT?
Saturday, November 22, 14

39. •Polymer
•Managed VM and Node.js
•Google Container Engine
Saturday, November 22, 14

40. QUESTIONS
?
Saturday, November 22, 14

41. Stay in touch :)
http://www.twindly.com
Astrid Paramita Mochtarram |
@astridparamita
I. Abiyasa Suhardi | @abiyasasuhardi
Saturday, November 22, 14