How to design a database to serve user requests?

Question

Database design

There is some entity Configuration with a set of parameters that is controlled by the user. For simplicity, the configuration of services inside the VPS, which indicates the number of units of CPU, Memory, Storage for each service. And we store these configurations in our system.

With the help of a request, the user sends a request for the allocation of resources to the VPS. The third party checks if this is possible and if so, then adapts to the new configuration or we get a refusal. If the failure, then we can not change the configuration. On the other hand, the user needs to be given the opportunity to adjust his configuration and we cannot just throw it away.

1. Are there any design patterns to serve such requests?
2. Is it necessary to store both states in the database: current and desired?
3. Create a new entity by transaction type? Or other thoughts?

I would be happy with examples, as well as links to articles, design patterns that can help solve the problem.

Answer 1

if an application for a new configuration is created on the basis of existing ones, then this is:
User - Configuration
User - Application - Configuration
if an application for a new configuration is built custom, then
User - Configuration
User - Application (Configuration in the field, for example, in json)