Re:I reverse engineered McDonalds’ internal API
by imglorp on Friday October 23, 2020 @08:35AM
(#24868770)
Meanwhile, Chick-fil-a is running Kubernetes at the edge for equipment, POS telemetry, and ML.
https://medium.com/@cfatechblog/bare-metal-k8s-clustering-at...
Re:I reverse engineered McDonalds’ internal API
by curryst on Friday October 23, 2020 @11:19AM
(#24870383)
Their tech stack is far more bleeding edge than I would have envisioned. I wish they gave an idea of why they chose to use k8s at the edge. I can see how containers are useful for deployment, and the fail-over built into Kubernetes is really nice, but I'm shocked that's the simplest/best way to do it at the edge.
I would have expected some VMWare product, just because it's "enterprisey". Shame on me for judging.
Re:I reverse engineered McDonalds’ internal API
by imglorp on Friday October 23, 2020 @01:02PM
(#24871541)
Deployments and monitoring are probably another draw. Same tools server and edge side.
Another project to keep an eye on is AWS's Greengrass which has a bunch of capability overlap, but a bunch of new ideas for edge and fog IoT also. I had a mixed experience with it but at least some ideas bear borrowing.
Re:I reverse engineered McDonalds’ internal API
by chapium on Thursday October 22, 2020 @09:55PM
(#24865291)
Not sure if this is the same thing, but I recall reading a case study in 2006 on McD's cloudifying their kitchen equipment. The project was apparently a huge failure and was eventually stopped due to runaway costs.
There was an old effort a long time ago where the machines were on a powerline-networking system (LONWorks) but that is dead and buried. The next-gen effort was ramping up a few years ago and I don't really know where it is now. The predictive analytics company they bought was a big part of it.