Yest another microservice technologies?

[Bartolomeus-649]

It would be really great if Microsoft could clearly state where they are going with all their different microservice technologies. Wise from experience and with a clear memory that Microsoft can just cancel and terminate just about anything without any warning or communication from one day to another, it would be great to know where you are going in the long run. This since if you are to base a huge enterprise project on something you need it to be around and not just be abandoned like, for example, Silverlight. Yu need to know that it will be around, supported by Microsoft, and that it will be actively developed, improved and maintained for at least 10+ years.

Also some other questions...

1. Which problem is ReactiveMachine a solution to?
2. When you have AMBROSIA, which supports coding stuff in C#, what does ReactiveMachine add which is not already possible to do in AMBROSIA?
3. How does this relate to ServiceFabric and Orleans?

[sebastianburckhardt]

This project is not being actively pursued at the moment. It was our initial foray into this space. But we have now joined forces with the Azure Durable Functions team, which has a similar mission, but is more specifically targeted at serverless application development, and production ready and shipping.

So, the current plan is to move ideas from from Reactive Machine into Azure Durable Functions. This has already happened, for example the implementation of Durable Entities and Criticial Sections is based on insights gathered here.