Why would a restaurant use this for membership point when a glorified Access db would work just as well?
Why would a restaurant use this for membership point when a glorified Access db would work just as well?
And then we'll take it higher!!
And for the record, an SMB was just an example of a small-time issuer as opposed to a massive ICO worth millions. But the fact is, we continue to iterate and rewrite things in technology. Why Dropbox when I have a thumb drive? Why CRM/Salesforce when I have a Rolodex? Why noSQL when... SQL? No one is saying blockchain technology will cure cancer or is imperative in bringing about a change.
Using Bancor does not mean that the SMB is doing this all from scratch. After all, how many restaurants do you see implementing their own POS system with in-house engineers? And to be honest, how airtight do you think a mom and pop shop's MS Access DB backup strategy would be? I would trust "food with blockchain" over "food with please-don't-die-on-me production DB."
OK so use Google Sheets instead of Access? Or anything? I don't get where the distributed, trustless, properties of blockchain tech make any sense for a centralized DB with only one source of truth (the restaurant).
That doesn't mean people can't or shouldn't explore in a yet-another-noSQL DB, a new MVC framework, a new low-level language, etc. This hypothetical store doesn't have to use blockchain technology, but it could and reap the benefits or potential harms of doing things the new way.