Integrate Mark Reply with airSlate SignNow

Integrate mark reply

hello everyone and welcome to software architecture monday my name is mark richards and in this lesson number 142 we'll talk about request reply messaging versus async notification a different kind of request reply model you can get a listing of all of my lessons in software architecture monday from my website developer2architect.com lessons or just go to my website and press on the lessons link now as most of you know most of the material that i do for software architecture monday does come from the two books that i wrote with neil ford recently the fundamentals of software architecture and software architecture the hard parts however as i mentioned in the last lesson sometimes the material comes from questions in the field and as a matter of fact that's what the content of this video is about a question that i received regarding request reply processing and i wanted to show you that now way back in lesson one the very first lesson i did in software architecture monday to kind of kick off the website i did talk about request reply processing and messaging the mechanisms of kind of how it works and different models within there using either temporary cues or a correlation id i wanted to now in this video expand on that to talk about two different techniques or models for request reply processing and the two models are request reply or async notification and i wanted to show you the differences between those as well as the implications and consequences and when you should use each model so let's talk about request reply messaging first and this is kind of a summary of what i was talking about in lesson one let's say we have an order placement service and a payment service now in this case payments required at the time of an order so i've got a message channel in between these two now a customer is going to go place an order and here's what happens with request reply messaging so the customer places the order uh order placement does what it needs to do and needs to apply the payment so it sends a message over to the payment service on a single channel and now sits and waits on that same channel for that payment to be applied and so the payment does what it needs to do responds back through that other message channel and then i respond back to the customer saying thank you for your order this is an example of the use of request reply messaging so because i say there's a single channel it's the same message channel but really it is in the form of two different cues that we use for request reply a request queue that i send a request on and a reply cue that i wait based on like for example a correlation id now a couple of things about request reply messaging first i want to emphasize...