Skip to main content
Software Engineering

Return to Question

Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
added 2 characters in body; edited title
Source Link
Tulains Córdova
Tulains Córdova
  • 39.5k
  • 13
  • 99
  • 155

Eventing solutions for javaJava legacy applications too old for real JMS queue/topic eventing?

What are some architectural solutions that can mimic eventing for systems (Java) that are too old to implement eventing solutions, such as conventional Queue/Topic based JMS messaging?

I have a system that is REST capable and needs to interface with other systems, but having it send messages would be the most ideal solution. However, it is too old to do so.

Are there any kindskind of architectural patterns/solutions that can provide capabilities like this?

Like perhaps some kind of framework which can act as a system in the middle, by fetching data from the legacy system over REST, then packing it into a format that's then sent over JMS?

Eventing solutions for java legacy applications too old for real JMS queue/topic eventing?

What are some architectural solutions that can mimic eventing for systems (Java) that are too old to implement eventing solutions, such as conventional Queue/Topic based JMS messaging?

I have a system that is REST capable and needs to interface with other systems, but having it send messages would be the most ideal solution. However, it is too old to do so.

Are there any kinds architectural patterns/solutions that can provide capabilities like this?

Like perhaps some kind of framework which can act as a system in the middle, by fetching data from the legacy system over REST, then packing it into a format that's then sent over JMS?

Eventing solutions for Java legacy applications too old for real JMS queue/topic eventing?

What are some architectural solutions that can mimic eventing for systems (Java) that are too old to implement eventing solutions, such as conventional Queue/Topic based JMS messaging?

I have a system that is REST capable and needs to interface with other systems, but having it send messages would be the most ideal solution. However, it is too old to do so.

Are there any kind of architectural patterns/solutions that can provide capabilities like this?

Like perhaps some kind of framework which can act as a system in the middle, by fetching data from the legacy system over REST, then packing it into a format that's then sent over JMS?

Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Source Link
adam bronfin
adam bronfin
  • 29
  • 1

Eventing solutions for java legacy applications too old for real JMS queue/topic eventing?

What are some architectural solutions that can mimic eventing for systems (Java) that are too old to implement eventing solutions, such as conventional Queue/Topic based JMS messaging?

I have a system that is REST capable and needs to interface with other systems, but having it send messages would be the most ideal solution. However, it is too old to do so.

Are there any kinds architectural patterns/solutions that can provide capabilities like this?

Like perhaps some kind of framework which can act as a system in the middle, by fetching data from the legacy system over REST, then packing it into a format that's then sent over JMS?