Architecture of a decentralized (distributed) application?

Question

PostgreSQL

Hello colleagues,
please recommend a template or an article on building a distributed web application. The theoretical task is how to ensure the operability of the branch if the Internet is gone, and there is no access to the main web application. So far, I've thought of running a copy of the application in each branch, and working offline when there is no Internet, and synchronizing data when a connection appears. Conditionally upload to each terminal according to the Docket container, and synchronize the data with the master according to the schedule.
Is this the normal approach? There is also the possibility of backup channels, but I want to achieve absolute high availability at such moments so that the business does not stop if all the backup channels are covered and there is no connection with the outside world.
I would appreciate links to current articles.
Thank you!

Answer 1

Have you heard of the CAP theorem?
You want to have accessibility and partition tolerance, so you must forego consistency. See AP systems.
Whether the approach is normal depends on the task, it is necessary to consider a specific situation and a specific business. If integrity constraints allow, then yes, normal. The plan for merging and resolving conflicts is only to be described in advance.