Transaction protection - question about node-json-db

[Belphemur]

Hello @PotOfCoffee2Go,

For a project that relies on multiple/concurrent access + atomicity of the data, I advise against json-db.
Json-DB is more a wrapper to JSON file that's great to manage configuration files or a small set of data.

In your case, you'd better use an RDBMS like Postgresql that would give you more security and better performance than json-DB.

[PotOfCoffee2Go]

Hi @Belphemur,

I kinda figured some sane person would recommend to use a RDBMS.

All of the data for the auction is on a MySql DB running on a AWS EC2 server. It holds all the stuff - the Guest info, login creds, etc. - as well as Item info, descriptions, images, and stuff. The auction exchange itself only needs around 8 fields - Item ID, current price, status and info on last bid (GuestID, time, bid amount, status). I already wrote the auction exchange using the MySql DB - establishing a Transaction, doing the writes, the Commit, etc.

The network latency though is right up there - so that is why I gave a shot using node-json-db because I've had great luck with it in the past; and running on OpenShift which has SSD drives - it's faster than fast. I do realize node-json-db was not designed to do this - but... hey, why not give it a shot!

Anyway, just figured out this morning - made a change where am now writing to a single collection with one push( ). Load testing has been running for hours now - no issues! ;) Not sure how many updates a second it can do as it out performs the number of bids that I can push across the network - how great is that!

So looking forward - I'm going to use it. We'll find out in October - donating my time to great non-profit Onyx & Breezy dedicated to animal welfare. Their live auction will be on it - so let's keep our fingers crossed. As well as publicly available on Github.

Thank you for your reply!