Sub-Document feature is released in 4.5 DP. Does it only reduces network traffic or it
also reduces disk I/O and memory useges ?
How large document can I design if the Sub-Document feature is supported ?
For example I designed a document contains daily around 100 events. If possible I’d like to
design yearly document which contains 100 * 356 events.
Reduce network bandwidth because you don’t have to send/receive full document across the network.
Latency improvement for get/set for large documents. In this case, only a small portion of the document needs to traverse the network, which reduces the latency.
Thank you for the reply and providing valuable information about Sub-Document.
How often will the documents get updated?
100 times everyday and 100 * 365 times per year.
Do you only need to read one day’s events or you need to read multiple day’s events?
Usually one day’s events but sometimes we need to traverse documents over days.
What’s your latency requirements for get/set?
We expect the latency should be the same as the document design is daily basis.