I have a scenario like this:
You have a factory line that works 24/7. Downtime is extremely expensive. The software that manages all the different parts must use a common database storage form. The main reason for this is to know what state the factory is in. For example, some products may be mixed using the same set of equipment and others. DEFINITELY no.
requirements:
- I want the software to be able to detect that an error in one part of the plant should cause the machine to stop at a distance of more than 1 km. therefore comparison data in plc is not an option.
- Frequently updated updates and updates in the factory environment
- Download (in computer terms) will be very low.
Systems process several hunderd assignments per day for which calculations / checks are performed, and then commands are sent for factory machines. Systems will be bored most of the time. The most important requirement is that the central computer system must be correct and always work.
I thought of using a dynamo-based database (riak or cassandra), where data is written to several machines with each machine that has the entire database
When one system is lowered, it will be lowered unchanged. A traditional sql database may be larger for updating when tables are changed, and this master slave is harder to configure.
What will be your decision?
. , db , .