this post was submitted on 16 Mar 2024
272 points (98.2% liked)
Technology
60102 readers
3180 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My question is why are the systems designed to be dependent to upstream services 24/7? Wouldn't a better approach be to have systems that can run disconnected, then simply upload/replicate data when a connection returns?
These are franchises, right?
I deployed such POS (Point of Sale) systems in the late 90's, because connectivity wasn't ubiquitous then. They were designed so franchises could upload/replicate however you needed: continuously, when a connection was available, on a schedule, etc. Some places had pooled telephone lines to achieve the needed throughput.
I get the mobile ordering being impacted, but why would you tie the local kiosk to a web service?
Didn't you hear? The future is the cloud!
Why host stuff locally when you can host it on someone else's computer, and have fun, exciting, and completely foreseeable failures like this...
The internet is now just AWS, Azure, GCP and Cloudflare.
There are many considerations where the fault lines should be. Somethings absolutely need upstream support and cannot just be buffered.. for example payment processing.
Shit happens and we DevOps people do everything we can to minimize it. That's why your apps might go down for like 2hrs a year.