Document modeling
In order to bring agility to applications that change business processes frequently demanded by its business environment, being schemaless is a good feature. In this methodology, you don't need to be concerned about structures of data initially while designing the application. This means as a developer, you don't need to worry about structures of a database schema, such as tables, or splitting information into various tables; instead, you should focus on application requirement and satisfying business needs.
I still recollect various moments related to design domain objects/tables, which I went through when I was a developer, especially the time when I had just graduated from engineering college and was into developing applications ...
Get Learning Couchbase now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
