Neuron ESB User Network

The Service Bus for the Connected Business

Hi, I'm new to Neuron but not completely new to messaging concepts. I am not getting a clear picture of the best 'Neuron way' to implement this scenario:

An application wishes to make a request of another system asynchronously and expects a reply. There's a defined timeout for getting the reply (could be days long) and the requesting app should be informed if the timeout occurs, thus 'failing' the attempt.

Forget about the message formats for a moment... could be POX or whatever.

So the primary success scenario is something like this:

App1 issues an asynchronous request to App2 and immediately gets a recept of some kind to eventually match to the reply message. App2 processes the request within the SLA timeout and posts a reply message, asynchronously, back to App1 with the receipt id somehow attached or embedded.

What is the simplest Neuron configuration that could accomplish this? Would I have to embed the receipt identifyer in the message myself, or is there a way to attach this to Neuron's message header?

Thanks!
Richard

Views: 281

Reply to This

Replies to This Discussion

Purely asynch with correlation in headers would be the most natural if you wanted one party to take action in its on receive that was a "response" to a message it had published earlier for something that went over days.

You could use the custom properties in the message header for the correlation values.
Ok, that's cool. Is this something you've seen before - any recommendations about the way to strucure the topics and parties in a situation like this... for example, let's say it's a simple CRUD type request for creating an account. Would you have a Topic/Subtopic hierarchy like so:

Accounts (Topic)
Accounts.Create.Request
Accounts.Create.Reply

Or would this be better split up in another way? I ask because I think you may have some reason why we would want to do it one way or another.
I think that's fine.

I use subtopics a lot for segmenting operations or for Service Connectors that respond to a Client Connector On Ramp.

You can align your subtopics with either operations or with states and that should work out well.

When it comes to long running operations I'm a much bigger fan of completey asynchronous messaging with with either context based (headers) or content based correlation.

I bought into state based engines for a while until I saw what happens under load and trying to debug complex compensation scenarios.

There's also the whole loosley coupled aspect...There's really nothing loosely coupled about state based engines...They need to maintain control of all aspects of processing otherwise they can't guarentee dehydration and rehydration, transactions, etc...

On the other hand, shuttling things asynchronously and managing persistence with an independent data store that also holds state transition information that allows you to know the next or previous step in a process or even store a complete state transition history is very scalable and will allow you to add functionality quickly.

You won't drag and drop your way there with the design tools many state based engines provide but you'll be able to add functionality, custom reporting, or switch out the backing store database (or even use multiple databases) much easier than if you start with a state based tool.

RSS

Neuron ESB Product Support Forums and Communities

Latest Activity

Anupama Nair posted a discussion

Marketo Adapter Invalid Token

Hi,We are using the Marketo adapter to push account updates to Marketo. It works well for some time then starts failing with Invalid Token unless restarted. Is there a configuration that can be done so it can auto refresh the token when required?Thanks!See More
Nov 6, 2023
Sayantini Basak posted a discussion

Maximum payload size(REST API) for requests interfacing to NeuronESB

I am new to Neuron ESB and in our current scenario,We need to process batch transactions comprising of ~1000 records and send them to Neuron ESB for further processing. I would like to understand what is the maximum size of payload that can be transferred using REST interface to Neuron ESB.See More
Jul 22, 2022
Profile IconRobert E Dunie and Sayantini Basak joined Neuron ESB User Network
Apr 28, 2022
Profile IconDayanand, Frederic C, Steffen Greve-Oksfeldt and 1 more joined Neuron ESB User Network
Mar 16, 2022
Profile IconCam Vong and Mitja Luznar joined Neuron ESB User Network
Jan 27, 2022
Profile IconWill Hitzges, Chad Parsons, michael larsen and 4 more joined Neuron ESB User Network
Jun 11, 2021
Anupama Nair posted a discussion

ODBC stored proc polling with temporary tables

We have set up an ODBC adapter to poll a stored proc.We found that if the stored proc has a temporary table defined the rows returned are always 0.Any idea why this would be and what we can do to get around it?See More
Dec 14, 2020
Prasanth Kharade is now a member of Neuron ESB User Network
Dec 30, 2019

Badge

Loading…

© 2024   Created by Neuron Admin.   Powered by

Badges  |  Report an Issue  |  Terms of Service