On Thu, Mar 24, 2016 at 8:55 PM, Claus Ibsen <claus.ib...@gmail.com> wrote:
> There has been a camel-rx component for several years now, but nobody > has shown interest in it. Nor is people screaming in this community > about reactive libraries. In fact people rely on Camel being "not in > the forefront" > A camel-rx component is an experiment rather than a component with a real use-case backing, IMHO. It's hard to find a use case for it. We're talking about different things. To me, Reactive is not a "module": it's a core pattern that you adopt in order to deal with inputs, data streams, RPC calls and concurrency. We're talking about *becoming* reactive at the heart to improve how we deal with concurrency and streams, not about little accessory. About Camel not being "in the forefront": that depends on the use case. For most of my customers, Camel is a at the heart of their ESB and it is a crucial component in their Enterprise Architecture. In some cases, Camel serves an API consumed by a public customer-facing site. Hence, I don't think we can generalise, and we don't have any survey numbers (AFAIK) to make any assertions about our users. Nor should we make assumptions based on what we see or not in the mailing lists or StackOverflow or other forums. Some people are more vocal when asking for help than others, so extracting information based on what one sees is vulnerable to a large set of biases. Back to the topic: I agree rewriting the core (whether in one direction or another) is a massive undertaking and not feasible for Camel 3. But rather than stopping the conversation at "let's push it to Camel 4", I'd like to hear people's thoughts. If the community wants to go in this direction at some point, we gotta start assembling interest. Does anybody feel strongly about this too? Cheers, *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging Engineer http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani Blog: raul.io | twitter: @raulvk <https://twitter.com/raulvk>
