You are viewing a single comment's thread from:
RE: Let's Talk About Fees & Functionality Coming in the @tippy Text-to-Tip Service!
Tip bots like any other instant service requires a solid foundation, ie scalability is to be solved from the ground up in day one, as well as availability. Especially a tipping service requires business critical availability since people get frustrated when it doesn't work. And frustrated people are bad for the success of the service. What also is very important is the absolute flawless handling of the tips, ie once accepted by the system, it shall never be lost, so data redundancy is required. @klye will the tip administration and value recording be done on the Steem blockchain? Or will the service gets its own DB?
The current version stores its user data in a custom structured database. However I do really like the idea of somehow having all user data and stats info stored on the STEEM blockchain..! I'm not sure I'll be able to figure that out in the 2 week deadline I've given myself but if by chance I do have a breakthrough on STEEM blockchain storage of data I'll certainly be attempting an implementation in future versions.
Just make sure to have a redundant DB and make sure when you have accepted a tip, the DB storage of the tip is accepted as well by the DB. This also counts for the deliver part of the tip. I suggest you make the accept and deliver patch independent, that seems to work better int he workflow, and you can for instance accept more tips incoming then sending out in high load situations. But, such engineering requires more work. I come from an industry where most of the engineering effort went into solidifying the software then the actual features the user sees; Required for business critical system with availability figures of 5 9's.