Guidance on replacement for Camel Spring Remoting

[mitpjones]

Hi,

the project I work on uses Camel Spring Remoting over JMS as its main method of communication between servers. Given that Spring Remoting has been removed from Spring 6 spring-projects/spring-framework#25379, we are looking for guidance on a replacement technology.

We have considered REST, gRPC and other technologies but so far nothing seems to lead to a simple migration path. For example with only a few lines and XML config on the client e.g.

    <bean id="dataManager" class="org.apache.camel.spring.remoting.CamelProxyFactoryBean" lazy-init="true">
        <property name="binding" value="false"/>
        <property name="serviceUrl" value="jms:queue:dataManager"/>
        <property name="serviceInterface" value="core.api.DataInterface"/>
    </bean>

and server e.g.

        <route>
            <from uri="jms:queue:dataManager"/>
            <to uri="bean:core.api.DataInterface"/>
        </route>

and no changes to the payload DTO classes (no annotations) we can make remote calls to any public method exposed on the target service, e.g. the client can inject the DataManager as a Spring bean and simply invoke any method which will in turn automagically make a remote call

dataManager.methodA(parameter1, parameter2);

In addition we haven't had to be concerned with Bi-directional relationships leading to circular references as the Java serialisation process is able to cope with this, where as it seems we may have to add additional instructions (annotations) to cope with this using other formats.

We have > 800 interfaces (services) proxied by the CamelProxyFactoryBean + > 700 DTOs and each service has many methods which equates to > 5000 methods able to be called remotely, so ideally we would like a drop in replacement or at least something that requires minimal change.

We also make use of JMS topics so that the servers can 'push' data back to the clients.

Thanks,

Tim

[artembilan]

May we know, please , what (or who) has led you here into Spring Integration project?

The Apache Camel in the picture is fully out of our scope. The Remoting removed from Spring Framework was never involved in Spring Integration.

I might come up with some solution for you, but that won’t be based on Apache Camel. Did you try to seek help over there, at Apache Camel community?

[mitpjones]

I posted here because it seemed from the way the documentation was organised ref https://docs.spring.io/spring-framework/docs/6.0.0-M1/reference/html/index.html, the best place to post a question was in this discussion group, happy to post elsewhere if you think not.

We are not wedded to Camel, transport, protocol etc, more important is the amount of change necessary to achieve similar behaviour.

No I have not posted to the Apache Camel group as I thought I would start here. I was hoping when the Spring team removed Spring remoting they might have had an idea of a good replacement and hence there would be more chance of a solution coming from this group.

I have discussed the impending changes to Java serialisation https://www.youtube.com/watch?v=mIbA2ymCWDs with an ActiveMQ developer and it's potential impact on the ActiveMQ/Artemis projects.