Apache Camel provided the sort of configurable architecture which allows web service messages to be determined dynamically during run time for web services that are hosted in Java environment.
I was wondering whether there is a similar/equivalent framework for applications written in c# and hosted in .Net/SharePoint environment?
We have compiled a list of solutions that reviewers voted as the best overall alternatives and competitors to Apache Camel, including IBM App Connect, WSO2 Enterprise Service Bus, Azure Service Bus, and TIBCO Cloud Integration (including BusinessWorks and Scribe).
Many open source projects and closed source technologies did not withstand the tests of time and have disappeared from the middleware stacks for good. After a decade, however, Apache Camel is still here and becoming even stronger for the next decade of integration.
It's especially suited to application integration – that means it's good if you need to consume, transform and route data between applications. Apache Camel is even more relevant today in the cloud era, where the number of applications in a typical enterprise just seems to be growing bigger and bigger.
As a matter of fact, Apache Camel is a complete integration framework, while Apache Kafka is a distributed messaging platform. So, at high level, they don't exclude each other. Apache Kafka can indeed well fit within the integration layer which can be designed as a Camel Route.
A bit late to this party, but might be of use to some people...
This wiki page has a list of alternatives - or it lists Camel as one of the options - https://en.wikipedia.org/wiki/Comparison_of_business_integration_software
Which leads me to suggest BizTalk - but that may be over the top for your requirements.
Apache Camel has not been ported to any other language. In a sense, there is no reason to port it. The whole point of Camel is Enterprise integration. All it really does is route and process messages.
If you need it to interact with a Sharepoint or .NET application, you can define a Camel Endpoint for whatever messaging or transport system you are using.
What problem are you trying to solve? I dont really know what you mean by:
allows web service messages to be determined dynamically during run time
The messages arent determined dynamically... whatever that means. Camel provides an implementation of many Enterprise Integration Patterns (EIP), but it needs to know the type of whatever message it is routing.
Camel has hundreds of automatic conversions, so it may seem like magic, but the truth is that jsut like anything else in Java, everything within Camel is type safe.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With