Reactive: IReactiveProcessing

Created on 18 May 2016  Â·  25Comments  Â·  Source: dotnet/reactive

what is the status of Rx v3 and the IReactiveProcessing that @bartdesmet demoed approx. 2yrs ago ?
please provide update

[area] Rx feature request

Most helpful comment

We're hoping to release a new batch of functionality later this year, based on internal developments that took place within the Bing organization. As part of this, we're looking at doing future developments in the area of our reactive programming cloud platform in the open here on GitHub. Currently, we're working out the details to transition parts of the technology to the .NET Foundation.

All 25 comments

We're hoping to release a new batch of functionality later this year, based on internal developments that took place within the Bing organization. As part of this, we're looking at doing future developments in the area of our reactive programming cloud platform in the open here on GitHub. Currently, we're working out the details to transition parts of the technology to the .NET Foundation.

Glad to see you're still around @bartdesmet. Hope to see rx.net support for .net core soon.

@bartdesmet that's great; really excited to think what this can bring to the table with #ServiceFabric and #Cloud complex event processing at scale; will the new functionality be available for coreclr and/or able to run on #ServiceFabric / #NanoServer ?

@bartdesmet in the meantime are there any samples of remote Qservable and/or QservableProvider like mentioned in @ch9 #techdays https://channel9.msdn.com/Events/TechDays/Techdays-2014-the-Netherlands/Event-processing-at-all-scales-with-Reactive-Extensions

Any update on progress or at least a roadmap?

@bartdesmet any update on IReactiveProcessing ?

@bartdesmet @onovotny any updates, understand your very busy; but if there is any more resources or information with regards the timeline and/or development or even an private preview program I’d be really interested? Oh and which branch should I be following as I can see there have be a few check ins with regard to work in progress in the last few weeks/months?

closed in error

any update on this ?

almost 3yrs past and nothing and no updates? guys will this even see the light of day ? even if it's a dead project an update would nice? also anthing around bonsi and weather this is also a dead-end ?

I don't know what IReactiveProcessing is. Do you have some details about it, the video perhaps, or some short description of the expected functionality?

@akarnokd IReactiveProcessing relates to Reactor in the very early days IReactiveProcessing was the interface that represented the cloud based process for the event stream created/referenced on the client; this more than likely has changed the name but I've not seen anything regards reactor or bonsi etc. or IReactiveProcessing …

It sounds out of scope to me. Rx.NET is about in-memory reactive data processing. Network/cloud/DB drivers are better suited in their own respective libraries.

@akarnokd I think you should review the above as it is a RX.NET and core project that @bartdesmet has been conducting and uses IQbservable for bing; its most definitely not out of scope for Rx

any updates ?

Here is another video by Bart going into more information about bonsai tree serialisation of IQbservable at NDC 2015 - https://vimeo.com/132192255

@bartdesmet did the bonsai tree code ever get released do you know ?

I've not seen anything with regard bonsitree, IMHO this is growing in importance especially with IoT devices data processing of IOT telemetry on the devices before sending to cloud.

2015 is a extremely long time ago in software development terms this is like a decade or two in real life. So I guess it dead or not happening :'l

You guys might want to check out Serialize.Linq, although it lacks all the async observable interfaces (IAsyncReactiveQbservable, IAsyncReactiveQbserver, etc).

I doubt anything will happen anytime soon in Rx.NET from our side in this respect.

This should be re-opened IMHO, @bartdesmet said above that a release was forthcoming and I would be very interested to know if/why that hasn't happened or if these features have been deemed obsolete in favor of a newer approach. IMHO I would truly love the ability to run RX in the cloud as a AzureFunction (with checkpointing) as was discussed. @akarnokd please re-open and/or seek updates with regards this maybe @bartdesmet can provide some background.

@bartdesmet any update? @akarnokd this surely shouldn't have been closed? the question is still valid and without any update or feedback to suggest what can/would be recommended to any remote rx in the cloud as shown by @bartdesmet

I'm not actively involved with Rx.NET at the moment and defer to @bartdesmet on the topic.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

weitzhandler picture weitzhandler  Â·  5Comments

davidnemeti picture davidnemeti  Â·  7Comments

Ptaah13 picture Ptaah13  Â·  4Comments

clairernovotny picture clairernovotny  Â·  3Comments

17-09 picture 17-09  Â·  5Comments