Blazor WASM (only) and no server backend? about ravendb.identity

[gabrielbarceloscn]

Hi @ellipsis-apps .

In case this works, you´ll expose RavenDB instance sensitive data to client code?

[JudahGabriel]

Hi @ellipsis-apps ,

The question boils down to this:, is Blazor's ".NET in the browser" WASM runtime able to run the RavenDB C# client? My answer is: probably? You'll probably want to ask this in the Raven mailing group.

RavenDB.Client is entirely managed code running on .NET Core, as I recall. Seems like a good candidate for running in Blazor's WASM runtime.

As @gabrielbarceloscn mentioned, not having a backend means you're introducing a new security concern. In RavenDB, security is done by certificates: to connect to the database, you need a certificate. Usually, your backend has that certificate. If you don't have a backend, then your Blazor app would need the certificate. And if your Blazor app has the certificate, so do your users. So you'd need to think about how that could work.

I'm looking for experience in alternatives to SQL databases & RavenDB seems to be one of the only ones offering free hosting for developers

You'll love Raven. It's stable and powerful and fast, and the tooling is fantastic, .NET is a first-class citizen, it's built with .NET Core. 😎 I use it for all my projects, and I dread ever having to write against SQL.