Is Eloquera or db4o better suited for my web application?

I'm considering using an object oriented database in Visual Studio .NET for my web application, which is basically a web store.

Which should I consider, Eloquera or db4o? Can I have some fresh perspective? A similar question was asked like 10 months ago - please also mention changes since then.

The features that I consider important are:

1. Ease of inte开发者_运维知识库gration into web application project.
2. Ease of querying using LINQ.
3. Ease of deployment upon release in IIS server.
4. Multi user support.

Looks like db4o could be a fit for your needs, but that depends on two factors:

1. If you're going to host your web store on a hosting provider db4o won't work in a limited trust environment

2. Depending on the number of simultaneous users, db4o could be a fit or not. As a rule of thumb I would say that if you're talking about more than 50 users hitting the db at the same time, then you should look at other options (one example: Versant Object Database).

Disclosure: I work for Versant and db4o.

Another option would be RavenDb -- it is more of a document database than an object database but it satisfies your requirements by and large:

• Easy Integration: insanely easy; use nuget
• Easy Linq: linq is the query platform
• Easy for IIS: pretty much set up an application pointed there and you are done
• Multi-User: yup.

I suggest Eloquera. All the pros of db4o (and more), less some cons...

Real World Experience of db4o and/or Eloquera Database

Eloquera is multihreaded, in opposite to db4o. So, if you expect more that a single visitor to your website, Eloquera is an obvious winner here.

Moreover, Eloquera provides the object-oriented and document-oriented APIs, which can be used together.