Until now we have used self-describing json. These days we prefer hocon for application configuration because:
Easier to add new optional fields without making breaking change for users
The hocon parsing library supports environment variables and system properties out of the box.
This change can be done in such a way that we still support SDJ as a legacy format, which will make upgrade path easier for users. We can take advantage of the fact that hocon is a superset of json.
Until now we have used self-describing json. These days we prefer hocon for application configuration because:
This change can be done in such a way that we still support SDJ as a legacy format, which will make upgrade path easier for users. We can take advantage of the fact that hocon is a superset of json.