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?
May I ask you why you would want to store booking slots?
I think the right approach is to recalculate available booking slots everytime (via the nettu-scheduler api) a customer asks for it. And then also store the confirmed booking timespan as a calendar event in nettu-scheduler so that the instructor will not be bookable again during that time.
You can have a look at this example: https://github.com/fmeringdal/nettu-scheduler/blob/master/ex...
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....
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.
Their backup plan was already executed: they switched from their testing methodology to acting as a service provider for somebody else's testing methodology (http://www.businessinsider.com/bill-maris-explains-why-gv-di... """So, we just had someone from our life-science investment team go into Walgreens and take the test. And it wasn't that difficult for anyone to determine that things may not be what they seem here."
That employee found that when he went to get a test done, Theranos wanted more than just a drop of blood in one of its "nanotainers." He denied a full venous blood draw, and ended up getting called back a week later because they wanted him to give more blood.""")
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.
