3 ms·
You don't need a full database, you just need well-specified serialization/deserialization. Typically this includes explicit versioning mechanisms, so the app c
by zozbot234 5y ago
You don't need a full database, you just need well-specified serialization/deserialization. Typically this includes explicit versioning mechanisms, so the app can be aware of what version it is dealing with and convert the format accordingly.
- jeff-davis 5y agoser/de only solves parsing problems and not much else. What about using duplicate user IDs? Or maybe many objects in the system need both the employee ID and the name (and the employee ID determines the name, obviously), and the employee changes their name, but it only updates some objects and not all? There are lots of ways data can be subtly inconsistent and a database is a big help preventing it.