consider a project that user can create auctions and others can make bids, i wonder if i need a DB or a big object can do the job.
let me explain this. this is an online job, user need to be online to see auctions and make a bid. app must fetch data from APIs and show 'em to user. no data must be out of date. so user must see what is exactly available on server side.
now i wonder if i need to have a database in my app and load these data to this DB or just have a big Object (singleton pattern) which has all fields (like auctions - bids - or any other data) and just use this object to my jobs.
in my vision i can't think about any data which i need to store offline, so what gains may DB still give me?
btw in second approach, if all classes are modeled and put in that object, it will exactly look like DB scheme