You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All snapshots in database are saved as Jsonb, there are currently two types in Kotlin that can be saved directly as Jsonb, String and jackson.databind.JsonNode. We should switch to String for snapshots in all entity class.
Reasons:
JsonNode will validate the data and ensure a valid json when being created, but we have core/kotlin serializer handles it.
JsonNode is slow, as each json key-value pair is saved as a node. The process time to create a JsonNode increases significantly as the size of snapshot increases.
JsonNode provides the passibility to work with the key-value pairs it contains. However, there are limited usage for this is webservices currently, and we should convert the snapshots into its corresponding domain/datatype before we work with them, or access them directly through database.
The text was updated successfully, but these errors were encountered:
All snapshots in database are saved as Jsonb, there are currently two types in Kotlin that can be saved directly as Jsonb,
String
andjackson.databind.JsonNode
. We should switch toString
for snapshots in all entity class.Reasons:
JsonNode
will validate the data and ensure a valid json when being created, but we have core/kotlin serializer handles it.The text was updated successfully, but these errors were encountered: