4 ms·
There's usually some way to "cheat" to make things easier. In this case, orders don't need to ask go into a single globally accessible instantaneously updated d
by fragmede 2y ago
There's usually some way to "cheat" to make things easier. In this case, orders don't need to ask go into a single globally accessible instantaneously updated database like BigTable. A McDonald's in San Francisco doesn't care what a McDonald's in Paris' customers have ordered right that second. Or even the one down the street. So the worst you could do is give each restaurant their own copy of the stack. And that stack meds to handle maybe 3 orders a minute? The busiest McDonald's still isn't going to be all that busy in orders per second, relative to a busy website. Everything you can do to optimize and use fewer resources per restaurant is an optimization and cost reduction problem,
but the base problem is inherently tractable. Chick-fil-A runs an Edge Kubernetes cluster at each of their 2800 restaurants.
- kstrauser 2y agoDefinitely. And that's the kind of thing that could certainly be managed by a "small" (at least compared to IBM) sized team. While it's not quite as simple as "Terraform it and call it good", it's probably not radically different from that, at least in concept.