Hub and Spoke Integration Solutions

[EnBaignantAvecPierre]

Wouldn't it depend on the purpose of the messaging system?

Tibco always used to be the preferred messaging for fire and forget pub-sub messaging where it doesn't matter whether the message gets there or not, or if it gets there multiple times (eg a stock price ticker).

If the message needs guaranteed once and once only delivery then Tibco loses the speed advantages that they have for fire and forget pub-sub communication and other solutions may be a better choice of technology (eg Oracle AQ).

I'd be surprised if there is a de facto solution these days.

Yes, this needs to be replayable.

[TheFaQQer]

Wouldn't it depend on the purpose of the messaging system?

Tibco always used to be the preferred messaging for fire and forget pub-sub messaging where it doesn't matter whether the message gets there or not, or if it gets there multiple times (eg a stock price ticker).

If the message needs guaranteed once and once only delivery then Tibco loses the speed advantages that they have for fire and forget pub-sub communication and other solutions may be a better choice of technology (eg Oracle AQ).

I'd be surprised if there is a de facto solution these days.

[stek]

Just wondering what's the de facto solution in the banking world to integrate core systems with a hub and spoke type architecture - I.e. one with a central repository to persist every transaction.

Past offerings included Tibco and xNetik.

Just wondering what's out there now.

Thank you.

Subscriber Trunk Dialling

[EnBaignantAvecPierre]

Just wondering what's the de facto solution in the banking world to integrate core systems with a hub and spoke type architecture - I.e. one with a central repository to persist every transaction.

Past offerings included Tibco and xNetik.

Just wondering what's out there now.

Thank you.