-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dead? #115
Comments
Well, it is a research project, not a product. So it never had a commitment of support or development. But there are some useful concepts here that can be learned. |
Hi all, I just want to let you know that Ambrosia is NOT dead. We are currently working on a number of very significant improvements, including scaleout, and support for other languages. Stay tuned :) |
Requiring Azure subscription will slow down the adoption of the technology. I understand that MS wants everyone of us to deploy on Azure, however even if I wanted there’s no Azure datacenter near where I live and the last time I checked the latency to the nearest one was horrible. Please provide alternative to Azure, otherwise it looks like a lock-in trap |
Hi @miroslavp :) In the fullness of time, we will open up the substitutability of Azure table with any persistent key value store. This being an MSR project, our resources are small, and contributions are welcome :) CRA already allows this, which is one source of Azure table usage. So someone needs to plumb this capability into Ambrosia. The other is for a bit of information like the latest log #. The logs and checkpoint are already storable anywhere in the filesystem, so there is no Azure dependency there. |
Hi @jongoldDB... great to hear this work is still ongoing! Have just asked over at the Durable Functions project if there are any plans to incorporate Ambrosia with the Azure Functions project? Could be wrong but feels like an excellent fit? |
Lots more goodies are coming this summer. Stay tuned :) |
So is Ambrosia another dead and abandoned project by Microsoft?
The text was updated successfully, but these errors were encountered: