No ! use mysql.... that Concurrency on sqlite have high depend... from HW..... (sqlite handles transaction one at time !)... 100 Concurrent Tx. (5 sec. each one)...the last pooled user must to wait 500 sec... to complete....
--- El mar 22-sep-09, CityDev <nab...@recitel.net> escribió: > De: CityDev <nab...@recitel.net> > Asunto: [sqlite] SQLite Suitability for Shopping Cart > Para: sqlite-users@sqlite.org > Fecha: martes, 22 de septiembre de 2009, 3:37 am > > I am building a shopping cart application that calls a web > service which > provides lists of documents and the documents themselves. > The user purchases > document images. The application will load lists into a > database, then build > pages from the stored lists. The database will also keep > track of > application state and store the retrieved documents for a > month. It must be > capable of supporting 100 simultaneous users. The maximum > list size is 8000 > documents which takes about 5 minutes to load from the web > service (in 5 > second transactions). There will be more than one front end > server. > > From this description, do you think SQLite is a valid > choice as the database > in this scenario? > -- > View this message in context: > http://www.nabble.com/SQLite-Suitability-for-Shopping-Cart-tp25530589p25530589.html > Sent from the SQLite mailing list archive at Nabble.com. > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > Yahoo! Cocina Encontra las mejores recetas con Yahoo! Cocina. http://ar.mujer.yahoo.com/cocina/ _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
