Conventions between applications
•
0 likes•674 views
This document discusses conventions for distributed applications to work together. It describes how a directory is used to map applications and resources, how events are published to allow for loose coupling between applications, and how deploying in small changes helps minimize costs and risks. Making a directory, publishing events, and deploying in small changes allows for shared ownership, teaching/learning, and discipline between teams.
Recommended
More Related Content
Similar to Conventions between applications
Similar to Conventions between applications (20)
Recently uploaded
Recently uploaded (20)
Conventions between applications
- 1. Conventions Between Applications Michael Ries @mmmries
- 5. Distributed System? Made of multiple applications working together
- 6. 2012 => 254 deploys/yr 2014 => 1,884 deploys/yr What we learned along the way everywhere on the internet
- 7. Make a Directory Publish Events Deploy Small Changes
- 8. Sample Project When a user is deleted we will cleanup their data
- 9. Abacus Amigo Sherlock Ballista Dispatch Bunyan Grunt Newman PersonaRelay Synchro HulkWormholeFirefly Dunaway AlfredBatcave Bullseye
- 10. The Directory Easily Navigable by Humans Used By Production Code http://media.tumblr.com/f9b5d822e963e6f6fc7fe7008b5ee8aa/tumblr_inline_mhbi8egCJz1qz4rgp.gif
- 11. Atlas - The Directory Protobuf (https://developers.google.com/protocol-buffers/) Map Resources to Applications Private Gem
- 14. Message Schema Migrations Backwards Compatible Changes Deprecations => Backwards Incompatible Changes
- 17. User (1.0.0) guid name Amigo Newman User (1.1.0) guid name email UserSearch User (1.1.0) ?✔
- 18. User (1.0.0) guid name Amigo Newman User (1.1.0) guid name email
- 19. User (1.0.0) guid name Amigo Newman User (2.0.0) guid name email first_name UserSearch User (2.0.0) ?X
- 20. User (1.0.0) guid name Amigo Newman User (1.2.0) guid name (deprecated) email first_name
- 21. User (1.0.0) guid name Amigo Newman User (1.2.0) guid name (deprecated) email first_name UserSearch User (1.2.0) ✔
- 22. Newman User (1.2.0) guid name (deprecated) email first_name newman$ rspec ......... DEPRECATION WARNING: Atlas::Amigo::User#name field usage is deprecated. (called from update at /Users/hqmq/code/ newman/app/services/atlas/ newman/notification_service.rb: 26)
- 23. The Directory Navigable by Team Members Used by Production Code Message Schema Well-defined Migration Semantics
- 24. Abacus Amigo Sherlock Ballista Dispatch Bunyan Grunt Newman PersonaRelay Synchro HulkWormholeFirefly Dunaway AlfredBatcave Bullseye
- 28. Events Low Coupling Similar To Controller
- 35. class UserSubscriber < ActionSubscriber::Base def deleted user = payload # Atlas::Amigo::User delete_accounts_for_user(user.guid) end end
- 37. ActionPublisher class User < ActiveRecord::Base include ActionPublisher::Syncable ... other code ... end
- 38. Events Low Coupling Similar To Controller Opt-in To Messages 1 Message Per Application
- 40. Amigo Abacus Persona Publish user.deleted message Cleanup Accounts on user.deleted Cleanup Members on user.deleted Newman Cleanup Notifications on user.deleted
- 41. 4 Tasks??? Cohesive Code Code Review Deploys Overhead
- 42. Deployment Costs Developer Time Developer Interruption System downtime
- 43. Zero-Downtime Matters 2012 2013 2014 254 Deploys 1,597 Deploys 1,884 Deploys Zero Downtime Implemented
- 44. Trebuchet Extension to Capistrano Deploy 1-by-1 Deploy in groups
- 45. Small Deploys Cohesive Codebases Automate Deploys Minimize Cost (interruption/time) Minimize Risk Code Review++
- 46. Make a Directory Publish Events Deploy Small Changes
- 47. Team >> Tech Shared Ownership Teaching / Learning Discipline http://gifrific.com/wp-content/uploads/2012/04/Punch-After-Celebration.gif