Hi,
I think add support for Table Storage is a good feature, as it's fast and reliable.
How I could contribute with this feature?
Thanks,
Gabriel Marquez
@gblmarquez we are working on allowing code contributions to this project but unfortunately it's not an option right now. But please do share your thoughts on this and perhaps it is something we can collaborate on in the very near future.
This would be actually interesting to keep the other implementations inside the core repository. However, not sure how easy the integration would be right now.
For example, I have the RavenDB and MongoDB implementations of the ASP.NET Identity. As far as I can guess, integration with K10 would be not possible as neither RavenDB nor MongoDB has K10 compliant clients yet.
@tugberkugurlu these ASP.NET vNext components can run on full .NET Framework as well so as a partial story you might be able to get things more easily running in that scenario. And then at the same time perhaps investigate what it would take to get RavenDB and MongoDB clients working on CoreCLR. In some experiments that we've done it turns out that some components are super easy to port: sometimes as simple as changing a few assembly references and maybe #ifdef-ing one or two lines. Of course, some components are a bit more involved to port...
@Eilon OK. I'll keep up to date to contribute on this feature, thanks! I already implemented and using on production a version of Identity with Azure Table Storage. It's so dame fast!
@tugberkugurlu We'll need to check if the SDK will be compliante, thanks for sharing your thoughts.
Just bumping this up to see if there's any progress on this front. /cc @rustd @Eilon
@MaximRouiller we are not planning on building this provider at this time, so no updates. If anyone wants to work on it I think we'd be happy to collaborate on the design.
Let's say that maybe I would perhaps be interested in doing it. ;-)
Who would I need to bother? Would it be integrated into the main framework or would it need to be a separate package?
Finally, if you need my email for further discussions let me know. :)
@MaximRouiller email me at elipton-AT-microsoft.com and I'll get you in touch with the right folks.
It would certainly be a separate package because everything is a separate package :smile: But as far as where it would ship, we should talk about that.
Email is fine for packaging details. You can post any questions in this repo to @HaoK @divega and we will be happy to help.
Looks like @MaximRouiller is going to take crack at this. Thank you!
I'll give it my best!
Hey @MaximRouiller do you need a hand? I've built my own MongoDB provider and have most likely run into similiar issues/challenges. I'm also condidering a Document DB provider.
I've looked at it and asked several people around and they all told me the same thing.
It's not a good idea as it won't be able to scale after a while. Perfect for small solutions but once you start to hit anything bigger, you will encounter performance issues and full table scan.
So at that point you'll need to migrate which won't be as easy. If you are on the cloud, there's already something out that is called Azure AD B2C which basically makes the whole username/password completely useless.
If you want to make a crack at it, go! :smile:
Table Storage doesn't make that much sense, but DocumentDB does :)
Oh absolutely. :smile: I've just decided to not waste time on Table Storage.
+1
Table Storage Provider working on Identity 3.0 RC1 - https://www.nuget.org/packages/ElCamino.AspNet.Identity.AzureTable/2.0.0-beta2
Unfortunately, I have not had the time to move the project to GitHub yet, it is in the works..- https://identityazuretable.codeplex.com/
Table Storage for Identity Core https://github.com/dlmelendez/identityazuretable .
Most helpful comment
Table Storage for Identity Core https://github.com/dlmelendez/identityazuretable .