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 for a corporate. Whenever I was a part of any application requirement discussion, I always had these questions at the back of my mind:
How does a domain object get stored in the database?
What will the table structures be?
How will I retrieve the...
