Knowledge-base
  • Home
  • Samman Technical Coaching
  • Software craftsmanship
    • Practices
      • Pair Programming
      • Code Review
      • Co-designs
      • Design sessions
      • Interview Domain Experts
      • Dev ethics
    • The Software Craftsman
    • Egoless Crafting
    • Technical debt workshop
    • Functional Programming made easy in C# with Language-ext
    • F# for OO programmers
    • Domain Modeling Made Functional
    • Testing
      • Clean Tests
      • Improve the design and testing of your micro-services through CDC Tests
        • CDC testing made simple with Pact
        • Pact broker : the missing piece of your Consumer-Driven Contract approach
      • Improve your test quality with Mutation testing
      • How to name our Unit Tests
      • How to write better assertions
    • Katas
      • TDD
        • Stack kata
        • Fizzbuzz
        • Outside-in TDD (London Style)
      • Improve your software quality with Property-Based Testing
        • A journey to Property-Based Testing
      • Clean Code
      • Clean Architecture
      • Write S.O.L.I.D code
      • Mocking
      • Gilded Rose (Approval Testing)
      • Mikado method
        • Mikado kata
      • Pure functions
      • Theatrical players refactoring Kata
        • Let's refactor (OOP style)
        • Let's refactor (FP style)
      • Functional Programming made easy in Java & C#
      • Refactoring journey
      • Refactoring du Bouchonnois
        • 1) Se faire une idée du code
        • 2) "Treat warnings as errors"
        • 3) Let's kill some mutants
        • 4) Améliorer la lisibilité des tests
        • 5) "Approve Everything"
        • 6) Définir des propriétés
        • 7) Tests d'architecture
        • 8) Use Cases
        • 9) Tell Don't Ask
        • 10) "Avoid Primitives" - Commands
        • 11) "Avoid Exceptions"
        • 12) "Event Sourcing"
    • Software Design X-Rays
      • Workshop
    • The Programmer's Brain
      • How to read code better
  • Software Architecture
    • Fundamentals of Software Architecture
    • Aligning Product & Software Design
    • DDD re-distilled
    • Test your architecture with Archunit
    • NoSQL
  • Agile coaching
    • How to run a Community of Practices (COP)
    • The developers — the forgotten of agility
      • The secrets to re-on-board the devs in agility
    • Coaching toolbox
      • Echelle
      • Learning expedition
    • How to improve Team Decision making ?
      • Decision Making Principles and Practices
    • Learning 3.0
    • Retrospectives
      • Back to the Future
      • Mission Impossible
      • Movie themes
      • Rétro dont vous êtes le héros
      • Sad/Mad/Glad
      • Speed boat
      • Star wars theme
      • Story cubes
    • Technical Agile Coaching with the Samman Method
    • Xanpan - a team centric agile method story
    • XTREM WATCH — Découvrez la puissance de la veille collective
    • Become a better speaker through peer feedback
    • Project-to-Product Principles
  • Leadership
    • Bref. J'ai pris une tarte dans la gueule (et ça fait extrêmement de bien)
    • Forward Summit 2020
    • Learn leadership from the Navy SEALs
    • Learn to lead and help your team(s) to be successful
    • Towards a learning organization and beyond
    • Leadership is language
  • Serious games
    • My serious games
    • Libérez vos entretiens d’embauche avec la gamification
    • How to create a game
    • How to debrief a game ?
    • Lego Serious Play (LSP)
      • LSP in your job interviews
  • Xtrem Reading
    • Cultivate Team Learning with Xtrem Reading
    • My Book Infographics
    • How to make book infographics
    • En route vers l’apprenance avec Xtrem Reading
    • Resources
      • Book notes
        • Agile People: A Radical Approach for HR & Managers
        • Agile testing : A Practical Guide for Testers and Agile Teams
        • Boite à outils de l'intelligence émotionnelle
        • Building a better business using Lego Serious Play method
        • Building evolutionary architectures
        • Code that fits in your head
        • Culture Agile
        • Culture is everything
        • Domain-Driven Design: The First 15 Years
        • Dynamic Reteaming - The Art and Wisdom of Changing Teams
        • How to avoid a Climate Disaster
        • La liberté du commandement
        • Réaliser ses rêves, ça s'apprend
        • Refactoring at Scale
        • Succeeding with OKRs in Agile
        • Team Topologies
        • The Good Life
        • Tu fais quoi dans la vie
        • Who Does What By How Much?
  • My Activity
    • Retour sur mon année 2020
Powered by GitBook
On this page
  • Objectives :
  • Connection - 10'
  • Concepts - 20'
  • Relational databases
  • ACID
  • Cons of relational databases
  • NoSQL
  • Different kind of NoSQL Databases
  • Why use NoSQL ?
  • Concrete Practice - 20'
  • Conclusion - 10'
  • Remember the past
  • Resources

Was this helpful?

  1. Software Architecture

NoSQL

Objectives :

  • Understand what does NoSQL mean

  • Understand the different kind of databases hidden behind this word

Connection - 10'

  • In pair list every Pros and Cons you have encountered with relational database

  • List every relational database you have already used

  • Group the answers

Concepts - 20'

Relational databases

  • Persist data

  • Concurrency control

  • Manage transactions in an ACID way

ACID

  • Atomicity

    • "all or nothing"

    • One part fails => the entire transaction fails

  • Consistency

    • Bring the database from one valid state to another

    • All defined rules, including constraints, cascades, triggers, and any combination are respected

  • Isolation

    • Concurrent execution

      • Would be obtained if transactions were executed sequentially

  • Durability

    • Transaction committed : it will remain

Cons of relational databases

  • Impedance mismatch

    • Relational data structures vs In-memory data structures

  • Performance

  • Distribution

  • Cost

NoSQL

Different kind of NoSQL Databases

Why use NoSQL ?

  • To improve programmer productivity : better matches an application needs

  • To improve data access performance

    • Through some combination of handling larger data volumes, reducing latency

  • Large volumes of rapidly changing structured, semi-structured, and unstructured data

  • Geographically distributed scale-out architecture

    • Instead of expensive, monolithic architecture

Concrete Practice - 20'

Let's play with a GraphDB call Neo4j for the next minutes :

  • Play with the Cypher queries

  • Play with the Graph Visualization

Conclusion - 10'

NoSQL does not mean “Death of SQL”

We can now create polyglot persistence :

  • Uses different data storage technologies to handle varying data storage needs

  • Can be applied : Anywhere in an organization/in a single application

Use the tool that fits the best your needs.

Remember the past

Think about the past few years, in which development you have made this kind of database would have been useful ?

  • Why ?

Resources

Key Value Stores

  • Aerospike

  • Apache Cassandra

  • Berkeley DB

  • Couchbase Server

  • Redis

  • Riak

Document DB

  • CouchDB

  • Elasticsearch

  • MongoDB

Graph DB

  • Neo4j

  • OrientDB

  • FlockDB

Wide Columns Family Stores

  • Cassandra

  • HBase

PreviousTest your architecture with ArchunitNextAgile coaching

Last updated 4 years ago

Was this helpful?

Connect to the

platform