Perhaps the following link can help: var claims = new List<Claim>(); claims.Add(new Claim(ClaimTypes.Name, “Brock”)); claims.Add(new Claim(ClaimTypes.Email, “[email protected]”)); var id = new ClaimsIdentity(claims,DefaultAuthenticationTypes.ApplicationCookie); var ctx = Request.GetOwinContext(); var authenticationManager = ctx.Authentication; authenticationManager.SignIn(id);
RavenDB: It has Lucene built-in for your full-text searches. It can be replicated. It supports sharding. It has a HTTP API so you can in principle use it from any platform. Cons: it’s AGPL licensed. Depending on your dev/server environment, you could consider it running on .NET a con. Also I’m not aware of the … Read more
if “20,000 concurrent writes” means inserts then I would go for CouchDB and use “_changes” api for triggers. But with 20.000 writes you would need a stable sharding aswell. Then you would better take a look at bigcouch And if “20.000” concurrent writes consist “mostly” updates I would go for MongoDB for sure, since Its … Read more
The only way I could reproduce the experience you describe is by intentionally creating a port conflict. By default, RavenDB’s web server hosts on port 8080, so if you are not changing raven’s port, then you must be hosting your WebApi application on port 8080. If this is not the case, please let me know … Read more