You use bad terminology. If you need application, you need production-ready database. Couchdb is production-ready, so, you can write application. "E-commerce application" is subset of "application", so, you can use couchdb for e-commerce.
2009/10/27 Paulo Cassiano <[email protected]>: > I'm totally newbie in CouchDB, but I belive it could be ready for production > use. True. I only was thinking about how could I develop some e-commerce app > using it as DB server... Did you think about it before? > > On Tue, Oct 27, 2009 at 1:50 PM, Elf <[email protected]> wrote: > >> Couchdb is ready for production use. >> >> 2009/10/27 Paulo Cassiano <[email protected]>: >> > OK, infact, that's could be a much bigger question. >> > >> > But I think I'm not the only guy to think about this... If YOU were asked >> to >> > do this, how did you do? >> > >> > On Tue, Oct 27, 2009 at 1:07 PM, Matt Goodall <[email protected] >> >wrote: >> > >> >> 2009/10/27 Paulo Cassiano <[email protected]>: >> >> > Every e-commerce app shows at least one product's picture, along with >> >> > descriptions and other useful information. Does CouchDB supports >> images - >> >> > JPEG, GIF and so on - files? >> >> >> >> Each CouchDB doc can have multiple attachments, see >> >> http://wiki.apache.org/couchdb/HTTP_Document_API#Attachments. >> >> >> >> I would say a "product" makes an almost perfect CouchDB document. The >> >> document itself could contain whatever data the product needed to >> >> describe it (description, options, price, bulk prices, etc, etc) and >> >> the images of the product would be its attachments. >> >> >> >> > >> >> > How could I use CouchDB in an e-commerce app? >> >> >> >> That's a much bigger question ;-). >> >> >> >> - Matt >> >> >> > >> >> >> >> -- >> ---------------- >> Best regards >> Elf >> mailto:[email protected] >> > -- ---------------- Best regards Elf mailto:[email protected]
