Before you understand the various considerations that need to be kept in mind while designing a document for any document-based system, particularly a Couchbase system, let me explain what a document really is and how it differs from RDBMS.
Often during my training sessions, participants have asked me what a document is really all about. They are often confused about document files, such as .pdf or .doc file formats. This terminology doesn't represent a file as you perceive in software world. Here, "document" means representation of information as perceived in reality or in the physical world. In reality, when we represent information, we discuss or represent it as a single complete document without breaking it into multiple documents and linking them to each other. For example, when we represent an invoice document, there are different sections, such as invoice, address, and items. If you need to store a domain object in a document, it will be represented as whole information...
