Introduction to Messaging
- 1. Introduction to Messaging Donald Belcham
- 2. wat?
- 6. Y U WANT?
- 21. Your App Your Backend App Your Backend App 2 Your Backend App 3 Your Backend App 1
Editor's Notes
- #4: Messaging is a way to communicate
- #5: Allows us to connect two or more completely separate systems
- #6: Systems don’t have to be tightly connected to work with each other.
- #8: There are a lot of demands placed on business software. Really they’re expectations, not demands...and many of them are entirely reasonable
- #9: Business expectations of how the application should work are at the top of the list
- #10: We’re left to figure out how to realize those business expectations via technology
- #11: The business has asked for things like Reliability USS Reliable served throughout WWII without any notable actions/problems/incidents
- #12: The business expects to have confirmation that a credit card has been charged before beginning to ship the product to the customer. No payment confirmation, no shipping.
- #13: We rely on transactions if possible or “manually” rolling back the data which is more likely
- #15: And Resiliency HMS Hardy...which was badly damaged by German destroyers during the Norway campaign of WWII and had to be run aground so as not to sink. The rising tide lifted her off the bottom and she capsized and was lost.
- #16: When an external system goes offline, they expect that it will not affect their systems
- #17: Usually this means we retry the request/communication with the 3rd party. But we can’t retry forever
- #18: Immediate retires, delayed retries, manual retries
- #19: And scalability
- #20: They want known spikes in traffic/usage to be handled without crippling the system and losing those sales/customers
- #21: Most commonly, infrastructure is built to the highest expected capacity and then run at a fraction of that for the majority of the time
- #23: They want their highest revenue customers to be treated with the priority that they deserve.
- #24: People start talking about multi-tenancy, stand alone systems for high value customers and other ‘duplicative’ solutions.
- #26: The way we historically, and currently, build apps makes overcoming these issues quite difficult.
- #27: Changing to messaging requires changing how you think Compensating actions instead of transactions “Events” and “commands” Idempotency “Immediate” usually means “less than X minutes/hours/days from now”