System of open joint business management

Project summary

The essence of the project is to write an operating system that is a platform for creating individual business management systems, which will be customized for a specific business, company or idea.
The whole system will be built on decentralized trailers.

When logging into the system, a person must install software on the device that will allow free hosting, he can specify the database storage locations (Any place can be used to store the required amount of data).

Since there are now two systems in the network, the Programs jointly decide for themselves where which part to host, choosing the most optimal solution.

The black zone means that this part of the program is not currently hosted on this device.
Once every n-th amount of time, the system will change its decision as to what to host with whom

Anyone from outside can visit the site. Despite the fact that front-end hosting happens on different devices, the domain remains the same.

The whole system is built on the principle that when accessing an element of the system (which can be hosted simultaneously on dozens of machines), the program itself decides which hosting the user or request will be directed to.
As a result, we have numerous copies of our system.
Each user of the subsystem who provided the opportunity to host our system can play several roles. Let's take a look at each of the roles and take a closer look at it.

front-end Hosting
Hosting of user presentation and functionality, graphical interaction with the system.

System-wide
general visual representation, excluding subsystem custom mappings.

Subsystem
Internal subsystem individually created

back-end Hosting
Hosting the server part of the system, providing the application logic as well as interacting with the database.

System-wide
Access to a shared database without direct access to database subsystems

Subsystem
Access only to internal subsystem databases

It turns out that each machine can act in one, or, if it is powerful enough, in several hosting functions.
It turns out that each user keeps copies of the shared system on their device?
Well, in fact, it is almost the same, but once in the n-th period of time there is a general exchange, so to speak, data update.
Each machine stores the entire system, consisting of 4 components that it can host, as well as the database with which part of the network communicates. As mentioned, the database can be stored directly on external storages. As mentioned above, the collegial decision of the system itself will determine which component is currently hosted on a particular device. The time through which the change of hosting components will take place is determined based on numerous factors.
And you must admit that it would be stupid if all the components of the main system were hosted in one subsystem at the same time, and in other subsystems it was not hosted at all. The system sees all the user, but breaks them into participants in the subsystems.
From all this, we get a decentralized, conditionally independent system with maximum security and data openness.
This project will encourage people to conduct business openly and honestly.
In general, we briefly went over in fact, write on all questions in a personal or by mail.