51–58 of 58 posts
Earlier quoted context omitted.
Instead of building the entire stack using (OS + K8) why not use Azure IoTEdge or AWS Greengrass for fleet management? These services seem to have solved a lot of the problems (low-footprint, redundancy, cloud management) already.
Cloud services like those tend to be limited in annoying ways. Also sometimes they simply vanish (@google). The lock in is also a negative.
> The goal of the Restaurant Edge Compute platform was to create a robust platform in each restaurant where our DevOps Product teams could deploy and manage applications to help Operators and Team Members keep pace with ever-growing business, whether in the kitchen, the supply chain, or in directly serving customers. > (Previous article) Our hypothesis: By making smarter kitchen equipment we can collect more data. By…
Mostly though, any data they collect will be very valuable, as forecasting is a core component of fast food logistics. Fast food lives and dies on efficiency.
Earlier quoted context omitted.
Instead of building the entire stack using (OS + K8) why not use Azure IoTEdge or AWS Greengrass for fleet management? These services seem to have solved a lot of the problems (low-footprint, redundancy, cloud management) already.
Cloud services like those tend to be limited in annoying ways. Also sometimes they simply vanish (@google). The lock in is also a negative.
Earlier quoted context omitted.
All I know is that I can be car #105 in line at Chick-fil-A and I'll get my food faster than being car #2 in line at McDonald's. Whatever they're doing is working.
Yeah, in my experience they are by far both the fastest and most consistent fast food restaurant. I've read they are also the highest revenue per-site chain.
And they have the best revenue per site.
Refreshing to see dynamic and nimble solutions from a large organization.
It's all the more important as walk ins and drive thrus reduce while delivers continue to rise.
Year 2023, FAA systems fail nationwide due to a “corrupt file” and Chick Fil A is highly redundant with a Kubernetes cluster running every store.
Earlier quoted context omitted.
Cloud services like those tend to be limited in annoying ways. Also sometimes they simply vanish (@google). The lock in is also a negative.
The lock in isn't a negative, it's just a cost. If you didn't build it yourself, that was a time and expertise savings. If they go away, you either just use the other vendor, or you have to pay for the time and expertise now, which you would have been paying anyway if you didn't use the vendored solution to begin with.
> just use the other vendor,
The point of lock in is to make it not a “just” to use a different vendor.
I also disagree with characterizing it as a cost. It is a negative because of its risk.
Earlier quoted context omitted.
When I was at Walmart the holy grail was edge compute in every store (which I think is now live). There is a mainframe in each store that powers point-of-sale, inventory, etc. But in terms of building modern apps, you couldn't assume 24/7 local connectivity was a thing or that it would be fast enough for what you wanted to do. Making each location its own failure domain was also a huge win. Imagine a cloud outage tak…
>There is a mainframe in each store Nope. vSphere clusters in every store. Possibly the biggest ‘field’ footprint of vSphere that exists.