3 ms·
Dual redundant internet(!), the wifi gear to reliably support that many devices, the cost of more expensive equipment, the added cost of support contracts to ke
by KennyBlanken 4y ago
Dual redundant internet(!), the wifi gear to reliably support that many devices, the cost of more expensive equipment, the added cost of support contracts to keep those fancy sensors working, especially since in a lot of locations they're probably the only food service place using them.
...and then the infrastructure of running the cloud services to support things like every restaurant's K8 cluster hitting a git server constantly throughout a day.
...and then there's the overhead of three separate dev ops teams.
etc.
- quanticle 4y agoSee my other comment [1] re: my experience at Potbelly. Restaurant usage is extremely bursty. For a lot of restaurants in business-y areas, you basically have a single spike of traffic from roughly 11:30 to 13:30 that drives >90% of the day's sales. You miss that, and you may as well write off the entire day's revenue. Investing in the redundancy (two internet connections, three servers, etc) to ensure that the point-of-sale system is online for that spike can be worth it, even for a relatively low-margin business. In fact, it might be more important for a low-margin business given the ephemeral nature of restaurant sales. It's not like e.g. Amazon, where if you're down for a few hours it doesn't matter, because customers will wait to buy their knick-knacks. If you're down for a lunch rush, you've lost that day's sales forever. After all, it's not as if customers are going to stay hungry and come back and buy two sandwiches tomorrow. They'll just go somewhere else for lunch. [1]: https://news.ycombinator.com/item?id=34350556 https://news.ycombinator.com/item?id=34350556