Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Containers and Databases

51 visualizaciones

Publicado el

Are databases in container are myth? Not really, like 10 years ago when VMs and containers were the same myth. This talk show the approach it's almost the same with some things "more modern" like containers, microservices, etc.

Publicado en: Tecnología
  • Sé el primero en comentar

  • Sé el primero en recomendar esto

Containers and Databases

  1. 1. Banco de dados em Containers Fernando IkePGConf.Brasil 2018
  2. 2. Cache/Buffer
  3. 3. Cache An auxiliary memory from which high-speed retrieval is possible.
  4. 4. Buffer A temporary memory area in which data is stored while it is being processed or transferred, especially one used while streaming video or downloading audio.
  5. 5.
  6. 6. Database cache Filesystem cache Disk cache Store data (disk)
  7. 7. What’s is Virtual Machine? “ efficient, isolated duplicate of a real computer machine...” Gerald Popek and Robert Goldberg
  8. 8. VM Infrastructure Hypervisor App A Artifact Bin/Libs App B Bin/Libs App C Bin/Libs Guest OS Guest OS Guest OS
  9. 9. What’s container? Container is a type of virtualization, more common call “operating-system-level virtualization”
  10. 10. Container Infrastructure Hypervisor Docker App A Artifact Bin/Libs App B Bin/Libs App C Bin/Libs
  11. 11. Ephemera Ephemera (singular: ephemeron) are any transitory written or printed matter not meant to be retained or preserved
  12. 12. Stateless application Applications don’t need to store anything in a persistent disk. Data application are storage in other part of architecture system
  13. 13. Stateful application Application that need to store “locally” data and need to recover that easy after an “interruption”
  14. 14. Cap Theorem
  15. 15. Union filesystem It allows files and directories of separate file systems, known as branches, to be transparently overlaid, forming a single coherent file system.
  16. 16. Container layers
  17. 17. Main filesytem for internal container data AUFS Overlayfs Overlayfs2 Device-Mapper Bind/Mount
  18. 18. Databases operation Plan what type of workload to use Maintain, organize and “improve” dataset together application Install security fix releases Archive “old” data (sanitize) Upgrade Database version Tuning OS, Database and Application
  19. 19. What’s means in OS handle... sysctl /proc /sys limits overcommit
  20. 20. What’s means in the PostgreSQL Shared Buffers WAL Max_connections Effective_cache_size Checkpoint_segments Random_page_cost
  21. 21. Container Volumes They are a mechanism for persisting data generated and/or used by container
  22. 22. Why to use PostgreSQL within containers Lower footprint to start Easy to change postgresql.conf and use git to have history change (tracking) Less surface attack in the “application Can “restrict” Linux Capabilities within container “Small” database by microservice Use always a Container Storage
  23. 23. Tips One database per type of workload Take care to restrict network, consider restrict database access only own application Push database log to Monitoring system/service Clusters and data replication are more complex Database use intensive CPU and IO, think if there is another service with the same workload type Database is prepare to support two version of application (Deploy strategies without downtime)
  24. 24. version: "3" services: db: image: postgres environment: - POSTGRES_USER=postgres - POSTGRES_PASSWORD=postgress - POSTGRES_DB=postgres ports: - "5433:5432" volumes: - pgdata:/var/lib/postgresql/data networks: - postgres volumes: pgdata: networks: postgres:
  25. 25. Demo
  26. 26. Demo code
  27. 27. ● Bruce Momjian - Performance tuning ● Docker Volumes ● Kubernetes Volumes ● Oxford Dictionaries ● Formal requirements for virtualizable third generation architectures - Gerald J. Popek and Robert P. Goldberg ● CAP Theorem and Distributed Database Management Systems References
  28. 28. // // // // // Contacts