Databases in containers

Databases in containers

A demystifying about database within modern containers presented in https://www.pgconf.com.br

168c322e7157a4cfffdeb88ab2309e02?s=128

Fernando ike

August 03, 2018
Tweet

Transcript

  1. 3.

    Cache An auxiliary memory from which high-speed retrieval is possible.

    https://en.oxforddictionaries.com/definition/cache
  2. 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. https://en.oxforddictionaries.com/definition/buffer
  3. 6.
  4. 8.

    What’s is Virtual Machine? “...an efficient, isolated duplicate of a

    real computer machine...” Gerald Popek and Robert Goldberg
  5. 9.
  6. 10.

    What’s container? Container is a type of virtualization, more common

    call “operating-system-level virtualization”
  7. 13.

    Stateless application Applications don’t need to store anything in a

    persistent disk. Data application are storage in other part of architecture system
  8. 14.

    Stateful application Application that need to store “locally” data and

    need to recover that easy after an “interruption”
  9. 16.

    Union filesystem It allows files and directories of separate file

    systems, known as branches, to be transparently overlaid, forming a single coherent file system.
  10. 19.

    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
  11. 23.

    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
  12. 24.

    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)
  13. 25.

    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:
  14. 26.
  15. 28.

    • 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