Choosing the right NoSQL type - You will learn when a key-value, document, column, graph, or object database is the better fit, so you can match the technology to actual application and business needs.
Informed architecture decisions - You will understand the CAP theorem and core NoSQL parameters, helping you assess trade-offs between consistency, availability, and tolerance to network partitions.
Performance-driven data modeling - You will practice modeling aggregates, objects, and relationships in NoSQL so you can design data structures that support fast reads, scaling, and simpler query handling.
Clearer view of data structures - You will organize your understanding of associative arrays, rows, column families, and indexes, making it easier to build a clear data model for different business scenarios.
Hands-on NoSQL database creation - You will learn the step-by-step process of creating a NoSQL database, which will help you prepare the environment, data structures, and assumptions for further solution development.
Smoother migration from relational databases - You will learn how to translate a relational model into NoSQL, reducing design mistakes, reshaping data structures consciously, and preserving the usefulness of existing data.
Handling relational needs in NoSQL - You will learn techniques such as multiple queries, caching, replication, denormalization, and nested data so you can manage relationship-heavy data effectively in NoSQL systems.
Comparing popular technologies - You will understand the strengths of Cassandra, HBase, and MongoDB, making it easier to choose the right platform for a project and justify your technical decisions to others.
NoSQL databases are introduced through their classification, core parameters, and the trade-offs described by the CAP theorem. The section also contrasts NoSQL with relational systems and uses Cassandra, Hbase, and Mongo to illustrate how these concepts appear in widely used platforms.
Different NoSQL families address different workload and structure requirements. This section compares key-value, column, document, graph, and object databases, and also situates other NoSQL variants so participants can distinguish their data models, strengths, and typical areas of use.
Data modeling in NoSQL depends on how aggregates, objects, and relationships are represented for specific usage patterns. Attention is given to shaping models that balance application needs with storage constraints, while avoiding direct transfer of relational conventions into non-relational structures.
At the architecture level, NoSQL data is organized differently than in row-oriented relational systems. The section explains databases as associative arrays, the role of rows and column families, and how indexes support access paths within models designed for distributed storage and high-volume processing.
Building a database in a NoSQL system involves defining the storage model around application use cases, data access, and scalability requirements. Participants work through the main stages of creating a database, from initial structure decisions to organizing data for efficient operations in a non-relational environment.
Migrating from a relational model to NoSQL begins with rethinking structures, access patterns, and constraints rather than copying tables directly. This part focuses on the conversion path, including how existing relational assumptions are translated into a model aligned with NoSQL storage and query behavior.
Relational-style access in NoSQL requires different design choices than joins and strict normalization. The section explains how multiple queries, caching, replication, denormalized structures, and nested data are used together to support read patterns and maintain acceptable consistency and performance.
Database fundamentals - You should understand tables, records, keys, and relationships so you can compare the relational approach with NoSQL and analyze the differences between data models with confidence.
Query and data operation basics - You should be able to perform basic data operations such as reading, writing, filtering, and updating, so moving into NoSQL models and structures will be much easier for you.
Data design basics - You should know the basics of designing data structures and understand why entities and links are defined, so you can work more effectively with aggregates, objects, and relations.
General IT orientation - You should feel comfortable with core IT terms such as server, network, application, and performance, so you can follow the architecture and operating principles of NoSQL databases.
