db4o Developer Community

When using db4o if the database is open with an exclusive lock on the file is it possible for .NET web applications to use this technology?  Even if you close the database connection when the application request ends won’t  this block the 50,000 other users that are using the my website and attempting to access the database.  I like the technology but I am not sure if this is the good fit for programming in the web domain.

What do you mean by "50.000 users"?

• 50.000 concurrent users (hitting your web-application nearly at the same time)? Here we're talking about transactions per second...
  or
  
• 50.000 people who will create an account on your site and store some data and only a percentage of the total users are visiting your site concurrently? Here we're talking about maximum database size...
  

Cheers, Maik

---

http://db4o.blogspot.com/

This would be 50,000 concurrent users hitting my web application at the same time.  Each user request will login into the system giving there user name and password.  After this I execute a query to return the profile data of the user.  This happens per user request.  Thanks for taking the time to answer this.  I think many new db4o programmers are concerned about his.

devCR2008:

This would be 50,000 concurrent users hitting my web application at the same time.

50.000 concurrent users is a pretty big load... there are not so many database-driven websites out there which could handle these kind of load.

You'll need to estimate how many transactions per second you're "concurrent users" will throw at your database. If we're talking about 50.000 transactions/sec, forget db4o (or any other ACID-compliant database) and better talk to the Google-Engineering-Team. If 50.000 concurrent users are coming down to about 100-1000 transactions/sec, db4o might be a fit (although some elaborate caching layer is needed).

Cheers, Maik

---

http://db4o.blogspot.com/

I was afraid you would say that.  It was really a choice between this and Big Table by you know who "Google."  This is a pretty big site with a lot of users.  I still like db4o technology. May be scalability might have to be the determining factor on this one.  Thanks