Service Oriented Architecture - Learn from the drug cartels

Do you want your app to allow scalability, failure resistance and fierce durability? learn how the real life service oriented organization did it successfully for years.

Transcript

1. Service Oriented Architecture Learn from the drug cartels
2. Hi! My name is Elad Meidar
3. Hi! http://github.com/eladmeidar
4. Hi! @eladmeidar
5. Service Oriented Architecture • Discrete modules • "Islands of responsibility" • Consumer and Producer services • Unassociated, autonomous, Loosely coupled units.
6. The Drug Cartel • Discrete modules • "Islands of responsibility" • Consumer and Producer services • Unassociated, autonomous, Loosely coupled units.
7. The Medellín Cartel • The first cartel to use a "distributed" method of operations. • At peak, covered more than 30% of the entire Colombian national export. • Yes. Cocaine.
8. The Service Oriented Drug Cartel • Each isolated unit had a specific role: ◦ Falcons (Halcons) ◦ Assassins (Sicarios) ◦ Lieutenants (Lugartenientes) ◦ Drug Lords (Capos) ◦ Overlords (Kingpins)
9. Falcons - Messengers and Monitors • Considered the "eyes and ears" of the streets. • They carry messages between the other units. • Simple and and clear role in the system, an easily replaced and scalable unit.
10. Assassins - pinpoint actions The armed group within the drug cartel that are responsible for carrying out assassinations, kidnappings, thefts, extortions and operating protections.
11. Lieutenants - Territory Managers Responsible for supervising the assassins and falcons within their own territory. They are allowed to carry out low-profile executions without permission from their bosses.
12. Drug Lords - Operations Managers Territory overlords, control the entire operation of a specific organization interest and a sizeable amount of people. responsible on all the procedures and activities within their territory.
13. Kingpins Kings are the source of everything. They determine what and who goes where and how. Usually there are several kingpins to assure continuity in case of early departure.
14. OK, Now what? Obviously we are not starting our own cartel
15. Same old drug dealing lady in a new dress SOA in the Web
16. • Messaging Systems ◦ Apollo ◦ RabbitMQ • Monitoring Tools ◦ Collectd ◦ NewRelic ◦ Organization Specific dashboards SOA's Falcons: Messaging and Monitoring
17. • Specific action driven workers • Wait on a specific message queue and process the request gracefully (Not so much in the case of real assassins). SOA's Assassins: Queue Workers
18. • Specific service back end stacks with a designated role and responsibility in the application flow. SOA's Lieutenants: Logical Business Units
19. • Front end layers that serve a complete response based on the results of a number of internal operations. SOA's Drug Lords
20. • Distribute the work and operation manifest between the stacks. SOA - Kingpins
21. SOA layout
22. This is (s)partitioning! Where to draw the line
23. Partitioning Guidelines • Iteration Speed • Logical Function • R/W Frequency • Join Frequency and the evil brother: • Data Replication
24. Iteration Speed Extracting services from a monolithic application as they become mature and stable enough. Probably the easiest partitioning method, but it can become complicated when your grasp the big picture as more and more parts of the system become "service-ready".
25. Logical Functionality Extract each logical element of your system into a specific service. • Pretty easy to identify logical domains and encapsulated operations. • Orchestration is a PITA. • Probably more costly than others
26. Read/Write Frequency Partitioning based on Read/Write frequency of services. Some services are made more simple than others based on need for caching or fast data layer. Defining the data access approach can lead to easier implementation of services (ex: you don't have to bother to expire frequently refreshing cache)
27. Join Frequency This method is about joining a few services that repeatedly talk to each other and by that to save expensive time doing expensive joins.
28. Data Replication is not EVIL! Data replication, made carefully, allows the application services to skip expensive joins for so called meta data - but makes the process of keeping data integrity complicated.
29. Back to the Cartel Partitioning by logical functionality
30. The kingpin hires a druglord to take on a specific city
31. The Druglord then finds a lieutenant to handle the "pandilla"
32. The lieutenant decides to assassinate a rival city leader
33. Sends a message to the assassin
34. Hasta la vista, Baby!
35. The Cartel - Partitioning example • By Iteration - The more the cartel grows, new pandillas are created. • Logical functionality - The members knows what they need to do. • Join Frequency - Top ranked members always have a Falcon nearby.
36. The End Questions?