The JSON-based dynamic-schema nature (aka schema-less nature) of document NoSQL databases is a fantastic opportunity for application
developers: ability to start storing and accessing data with minimal effort and setup, flexibility, fast and easy evolution. But moving to
NoSQL requires a mind-shift, a new methodology, and new tools to leverage new capabilities such as: polymorphism, embedding, denormalization,
and sharding. This data modeling course highlights the differences in the lifecycle, purpose, roles, and approach for data modeling for
NoSQL in an Agile development environment. It covers in depth the design patterns and modeling techniques for various representative use
cases and illustrates the patterns and best practices, including specific aspects of different NoSQL database vendors.
Testimonial: "Thank you so much for delivering the course and the great disruptive messages! Your provoking perspectives really helps!
We are changing the culture with the new Agile/DDD/modernization path that my organization has committed to. Your class helps us greatly not only
in NoSQL modeling principles, but building and forming the new culture that aligns with the new direction."
Lead Information Architect, Fortune 100 insurance company
• This class is a complete data modeling course for NoSQL, containing practical techniques for producing NoSQL physical data models.
• Participants will learn NoSQL schema design patterns applied to different illustrative use cases, including the migration from relational SQL schemas to denormalized schemas optimized to leverage the capabilities of NoSQL technology.
• Participants will learn not only how to build a NoSQL physical data model, but how to build it well, taking into account the differences with traditional SQL data modeling, as well as taking into account NoSQL vendor-specific aspects.
• The course also includes hands-on training for the Hackolade application, including exercises with general as well as advanced features.
Anyone with one or more of these terms in their job title: "data", "analyst", "architect", "developer", "database", and "modeler"