Chick Fil A's Edge Enterprise Architecture
1–10 of 58 posts
Re: Chick Fil A's Edge Enterprise Architecture
#2Re: Chick Fil A's Edge Enterprise Architecture
#3But why?
https://medium.com/chick-fil-atech/enterprise-restaurant-com...
Re: Chick Fil A's Edge Enterprise Architecture
#4Re: Chick Fil A's Edge Enterprise Architecture
#5[flagged]
[1]: https://medium.com/chick-fil-atech/edge-computing-at-chick-f...
Re: Chick Fil A's Edge Enterprise Architecture
#6But why?
The previous article linked in the post goes more into the "Why" https://medium.com/chick-fil-atech/enterprise-restaurant-com...
Re: Chick Fil A's Edge Enterprise Architecture
#7[flagged]
It's easy to have a low-effort cynical take about Chick-Fil-A's use of Kubernetes in its restaurants, but the actual post outlining why they chose to provision each restaurant with a 3-node Kubernetes cluster [1] makes a fairly compelling argument. Simply put, they needed to ensure that their point-of-sale terminals had bulletproof reliability, and they wanted to do it in a way that leveraged commodity hardware. The…
It's not just CFA. I for some reason watched a Taco Bell video on LinkedIn that layed out one small problem regarding the ability to accept orders, and how a -completely- new k8s microservice architecture addressed it. This smells a lot of the same, mixed in with more tech overoptimism. GE had the same spiels 10 years ago, with better use cases, and realized most of it was a dead end.
Re: Chick Fil A's Edge Enterprise Architecture
#8But why?
Re: Chick Fil A's Edge Enterprise Architecture
#9But why?
Making each location its own failure domain was also a huge win. Imagine a cloud outage taking out hundreds of stores.
Re: Chick Fil A's Edge Enterprise Architecture
#10[flagged]