Details
-
Epic
-
Resolution: Won't Fix
-
Major
-
None
-
None
-
None
-
Data modelling doc improvements
-
To Do
-
1
Description
With a push from DOC-9227 and some other thoughts on how data modelling and services are best introduced.
- identify scope of work
- consider how these topics are best presented and linked
- KV (data-service),
- subdocument operations,
- "Data Structures" (the Redis-parity features that seems under-surfaced in docs. The documentation looks useful with regard to the JSON data modelling, but that may be illusory if it's actually specifically for that one feature?)
- json modelling etc.
- basic howto (Hakim's frustrations with e.g. NodeJS vs Java difference)
- any discussion of impedance mismatch between native data structures and the JSON as handled by CB
- For example JSONValue only including Array/Object, whereas JSON since Ecma 404 allows number, string, boolean, null
- date handling
- representing objects
- other JSON best practices
- see also https://docs.couchbase.com/java-sdk/current/concept-docs/data-services.html this is a great page, but a bit hidden away.