1. Ruby and Rails,
as secret weapon to build your
service-oriented apps
Friday, July 15, 2011

2. Felipe Talavera
@flype
Friday, July 15, 2011

3. Agenda
- What’s a service?
- Peertransfer case
- A Typical rails application
- Advantages of the services approach
- Partitioning in services
- Ruby Toolbox
Friday, July 15, 2011

4. What is a service?
System that respond to HTTP requests:
Twitter API, Amazon S3 API, New York Times API
System that provides functionality through a standard interface:
MySQL, Memcached, RabbitMQ, ...
Friday, July 15, 2011

5. Service-oriented design
Friday, July 15, 2011

6. Service-oriented design is about creating
systems that group functionality around
logical function and business practices.
Friday, July 15, 2011

7. Services should be designed to be
interoperable and reusable.
Friday, July 15, 2011

8. Splitting up parts into components that can
be iterated on, improved, and fixed without
having to test and verify all the other
components when an individual is updated
or added.
Friday, July 15, 2011

9. Usually entails a trade-off between
complexity and iteration speed.
Friday, July 15, 2011

10. Amazon AWS
Every piece of the AWS architecture is exposed as a web
service, low-level system components exposed through
a services layer.
S3, SQS, SimpleDB, CloudFront, EC2
Friday, July 15, 2011

11. Friday, July 15, 2011

12. Friday, July 15, 2011

13. The Rails development style is all
about quick iterations.
Friday, July 15, 2011

14. A Typical rails Application
Friday, July 15, 2011

15. A Typical rails Application
Friday, July 15, 2011

16. The key to pairing Rails applications
with services is to use Rails for its strengths
and switch over to services when a
more stable approach is required
Friday, July 15, 2011

17. Service-oriented systems sacrifice iteration
speed for stability, reuse, and robustness.
Friday, July 15, 2011

18. Advantages of using services than
a typical monolithic application:
Friday, July 15, 2011

19. Isolation...
Friday, July 15, 2011

20. Business Logic
Isolation
Friday, July 15, 2011

21. Shared system
isolation
Friday, July 15, 2011

22. Full Isolation
Friday, July 15, 2011

23. Testing in Isolation
Friday, July 15, 2011

24. Robustness
Friday, July 15, 2011

25. Scalability
Friday, July 15, 2011

26. Scalability on team
and size
Friday, July 15, 2011

27. Reduces complexity
in the codebase
Friday, July 15, 2011

28. Agility
Friday, July 15, 2011

29. Interoperability
Friday, July 15, 2011

30. Partitioning
Functionality into
Separate Services:
Friday, July 15, 2011

31. Partitioning on
iteration speed
Friday, July 15, 2011

32. Partitioning on
Logical Function
Friday, July 15, 2011

33. Partition on Read/Write
frequencies
Friday, July 15, 2011

34. Partition on Join
Frequency
Friday, July 15, 2011

35. Versioning
• http://localhost:3000/api/v1/users/1
• http://localhost:3000/users/1?version=1
• http://localhost:3000/api/v2/users/1
Friday, July 15, 2011

36. Downsides
Releases dependencies nightmare
Smoke test suit mandatory
More moving parts and integration points
Trivial rails stuff gets harder
Failure tolerance is hard
Friday, July 15, 2011

37. Ruby Toolbox
Friday, July 15, 2011

38. JRuby
Friday, July 15, 2011

39. Rails
Friday, July 15, 2011

40. Sinatra
Friday, July 15, 2011

41. Goliath
Friday, July 15, 2011

42. Eventmachine
Friday, July 15, 2011

43. ActiveResource
Friday, July 15, 2011

44. HTTParty / Typhoeus
Friday, July 15, 2011

45. Foreman
Friday, July 15, 2011

46. Vagrant
Friday, July 15, 2011

47. AMQP
Friday, July 15, 2011

48. Conclusion
Friday, July 15, 2011

49. books
Enterprise Integration
Patterns Designing,
Building, and Deploying
Messaging Solutions
Friday, July 15, 2011

50. Questions?
Friday, July 15, 2011

51. We are hiring!
peertransfer.com
Friday, July 15, 2011

52. Friday, July 15, 2011

53. Friday, July 15, 2011

54. Friday, July 15, 2011

55. Thanks!
Friday, July 15, 2011