How We Use Ruby at MobME Wireless

This is how we use Ruby for backend infrastructure work.

Transcript

1. How we use Ruby @mobmewireless Vishnu Gopal
2. About ME Vishnu Gopal CTO, MobME Wireless SlideShare Inc Human-Computer Interaction at UCL, London twitter.com/vishnugopal
3. MobME Wireless Mobile VAS company: SMS, USSD, IVR Ruby is our primary language We don’t do much “web” development Ruby as a systems glue language www.mobme.in twitter.com/mobmewireless
4. systems glue as in?
5. we have backend apps written in C
6. OR WE HAVE an API from a client
7. we need to build admin interfaces
8. plug those into web interfaces
9. services that load data into those systems
10. services that take backups, fetch reports
11. services that collect data from ports
12. synchronous service
13. Asynchronous service
14. You folks probably do this with delayed_JOB
15. logging, accounting, control, responsibility
16. a separate service worker
17. sync_Service GEM
18. sync_Service GEM
19. ASYNC_SERVICE GEM
20. when you want to defer something, you need a queue
21. “quick and dirty, more flexible queues”
22. “enterprise-grade queues”
23. A Generic queue implementation
24. true_QUEUE RUBYGEM
25. true_QUEUE RUBYGEM
26. true_QUEUE RUBYGEM
27. TRUE_QUEUE GEM
28. Build all our vas apps
29. Voice APPS: OBD & IVR
30. Adhearsion Ruby interface to asterisk
31. Adhearsion
32. USSD Applications
33. homegrown framework Want to OpenSource
34. ussd renderer redux
35. admin interfaces
36. ADMIN INTERFACES
37. Twitter Bootstrap
38. abstract away enterprisey APIS
39. SAVON
40. SAVON
41. SAVON
42. On and ON....
43. internal technology recommendations Want to OpenSource
44. Finis
45. Questions? We are hiring!