Timeline for Passing transient information between two systems
Current License: CC BY-SA 4.0
        8 events
    
    | when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 14, 2019 at 20:36 | answer | added | JimmyJames | timeline score: 0 | |
| May 14, 2019 at 18:56 | comment | added | Hero Wanders | Is it right that some teams don't want to provide that additional info when sending Topic1 events? Perhaps introducing an augmented Topic1a with events allowing to transfer the same data as Topic1 events PLUS your information specific to A is the solution? B needs to subscribe to it and perform its extended processing only on that topic's events. | |
| May 14, 2019 at 16:25 | answer | added | ben rudgers | timeline score: 2 | |
| May 14, 2019 at 13:57 | comment | added | Filip Milovanović | "which have their priorities and concerns about passing this information" - could you edit the question to expand on that a bit? Seems like this is one of the key sources of the problem, so help us understand what is actually going on. What is the nature of these concerns? In what ways this affects them? Do they read and/or rearange this information, or simply pass it along without examining it? Maybe you just need better interfaces between the systems/services. | |
| May 14, 2019 at 12:55 | comment | added | antonro | @GregBurghardt We don't need only to know that other tasks have completed, we need some pieces of information. Also, I'm not sure that talking about 'main task' would be correct, I'd rather talk about most-upstream service and other downstream services. | |
| May 14, 2019 at 12:51 | history | edited | antonro | CC BY-SA 4.0 | 
        
            
             
                
                    Clarify flow 
                
             
        
     | 
| May 14, 2019 at 12:44 | comment | added | Greg Burghardt | Are you sure you don't just need to know that all of the other sub tasks have completed? Maybe each sub task should publish an event when it is done, and the main task can listen for these events and collect all the necessary information. Sounds like this will need to turn into a very asynchronous process. | |
| May 14, 2019 at 12:37 | history | asked | antonro | CC BY-SA 4.0 |