Data objects/classes and decoupling?

[JimPanse2k19]

Hello,
i am pretty new to pimcore and i wanna understand the fundamentals completely before deciding for using the system. So my question might be very basic.

There is a backend, were users can create data objects which will be reflected 1:1 in PHP classes. Those are generated automatically.

What comes directly to my mind:
Some administrative users (usually not a developer, but some "pim manager" or so) will have access to create/change those classes/objects in the backend because for example a "sku" should be named now an "skuNumber", or "sku" is now "SKU" etc.

How to ensure that these classes are consistent on the code side?

I am very afraid ending up in a mess where some user changing the "data model" in the backoffice, whilst a developer on the backend side is permanently adjusting the php code ... this includes renaming of properties, deleting them, renaming the objects etc.

How do you ideally deal with it?

I am asking, because I am usually used to see the data model defined/declared not from a backoffice by a user but on the code side.

But maybe I am missing a core concept here (?)

[dpfaffenbauer]

we usually don't allow anyone on a production system to change the class-definition. If you need a data-model that needs to be changed by a PIM Manager, you can either use the classification store (which is sort of a EAV Model) or build it with something like Advanced Many-to-Many Field (which is a custom made EAV Model).

I am doing Pimcore since 2012, and that was never a issue.

[JimPanse2k19]

Thanks. I will have a look at the "classification store".

So is there maybe a way around to completely block the creation/modification via backend, but instead create the model on the code side and reflect them to the backend? Unfortunately, my experience here was always like "whenever someone can change something, something will be changed by someone". For me it feels really off to give a user the power to directly break the backend implementation by just modifying data in the backoffice.

[dpfaffenbauer]

AFAIK: Running in Prod env, with debug disabled, you can't save classes anyway. Pimcore disables that.

Users usually don't get the permission to change it. Our devs have full admin, but they know what they do. We do these changes in the class-definitions locally and deploy them to prod.