Well, I was thinking of saving the booking slots presented to the customers for data purposes. Also, I was thinking that it might help to store the presented slots in case someone else books it before the person decides to reserve. This way eliminating the option in realtime might be easier and without having to recalculate all the remaining available slots again? But maybe there is a better solution to this....
I am trying to build a SAAS service for booking services. One of the engineering issues I ask myself is if the following will become an issue in the future: do I save all the options of slots available I show each customer in the database or do I just calculate the slots virtually and save only the confirmed bookings?
For myself I would prefer a solution were I would still die but can retain all my functions until that day (mental performance, muscle mass, strong bones, bodily functions, etc).
It would be great if Google drive wouldn't use up my MacBook's battery so fast. All the time my cpu usage is at 100% when using Google Backup and sync. Something that other competitors have managed to do better than Google. Using dropbox at the moment.
Most people just act irrational and maybe can't really see how much you actually contribute to the organization. We humans are really biased when it comes to choices.
Why don't you try out Meteor? I found it really easy to work with. You could probably go through the whole book tutorial (discovermeteor.com) in 20 hours. If you don't end up using it on production; it might help you with faster prototyping.