NoSQL databases are famous for their scalability, flexibility, fast and easy evolution, and for providing the ability to start storing and accessing data with minimal effort and setup. But with so much buzz around the terms NoSQL, schemaless, and non-relational, is it realistic to think that one can actually design an application with no structure, no schema, and no relationships? Or do some best practices from the ‘old world’ still apply to the ‘new world’? One such best practice is physical data modeling, whether beforehand, so projects are thought through, or after the fact, so proper documentation is maintained and shared.
In this session we will review how polymorphic or seemingly unstructured forms are handled, and how emerging modeling tools, designed specifically for NoSQL, help migrate from SQL databases.
A mind shift is required to move from the normalized world of relational databases to denormalization and schema-on-read. We will outline a method to start thinking in terms of queries and data representation, rather than in terms of storage.
In an Agile Development environment, you will see how a database model helps evaluate design options beforehand, think through the implications of different alternatives, and recognize potential hurdles before committing sizable amounts of development effort.
Each NoSQL database stores information in a different manner, with implications on scalability, performance, and data access flexibility. We will perform a quick overview of the different approaches of the leading NoSQL database vendors.