Improving Inter Service Communication

In times when applications get more and more split up into small pieces that have to communicate with each other it's critical to have systems in place that make this communication as trouble-free as possible. This talk covers what we did at Engine Yard to improve our inter service communication and how you can apply that to your own infrastructure. It also covers how this can change the way you are developing services, make building new ideas easier, and how it can make you a better developer.

Transcript

1. Improving InTER Service C ommunication
2. am Thorben Work for engineyard am known as wal I ki S
9. APPBESITY
19. (c) 2008 UrbanRail.Net (R. Schwandl)
23. Information Gap
24. Explicit distribution of information
25. Explicit distribution of information IMPLICIT
26. Share everything!
27. Share everything!
28. O H W
29. PubSub
30. Publisher
31. Subscriber
32. THing
33. subscribe to Y subscribe to X
34. Slob!
35. Slob!
36. Slob! LOG.* LOG.MEMORY.* LOG.MEMORY.INFO
37. Slob!
40. publish data easily?
41. publish data easily? Instrument your ORM!
42. pROBLEMS
43. App App Redis Web cluster
44. Web Service
45. Web Pub sub Service
46. Redis auth is Puristic
47. Pubsub cluster nginx auth redis lua redis2 nginx http
48. But this sounds s t u p i d
49. it is But this sounds s t u p i d
50. Share everything
51. empower everyone
52. custo ! mers ! ! ! ! ! ! !
53. Dankeschön Credits: Kevin Christopher (http://www.kcfonts.com) Paul Townsend (http://www.flickr.com/photos/brizzlebornandbred/6136387805/) Doug Baulos (http://www.flickr.com/photos/machinewithnoname/2587364509/)