Please enable JavaScript.

Coggle requires JavaScript to display documents.

Software Engineering - Coggle Diagram

- - - - T-shirt size
      - Points
      - Days
      - PERT ((O+4M+P)/6)
- - - - Indexes
        
        GIN (Generalized Inverted Index)
      - Scalability
        
        Connection pooling
        
        pgBouncer [1]
        
        Horizontal scaling
        
        read path
        
        load balancers
        
        slave nodes
        
        keepalived
        
        write path
        
        need external tool
      - Temporal / Bi-temporal
        
        https://www.pgcon.org/2019/schedule/attachments/552_slides.pdf
        
        https://www.timescale.com/
      - High Availability
        
        https://www.pgbarman.org
        
        Observability
        
        CPU usage
        
        memory usage
        
        disk usage
        
        # connections
        
        # running queries
        
        index usage
        
        "bloat"
        
        replication lag
      - "Columns Tetris"
        
        8 bytes columns first,
        
        then 4 bytes columns,
        
        then 2 bytes columns,
        
        and finally 1 byte columns
        
        see also
        
        https://www.postgresql.org/docs/current/datatype-numeric.html
        
        https://www.2ndquadrant.com/en/blog/on-rocks-and-sand/
  - - - Efficiently store
        
        jsonb / PostgreSQL
        
        BSON / MongoDB
      - Efficiently query
        
        PostgreSQL's jsonb GIN indexes
        
        MongoDB's BSON indexes
      - Benchmarks
        
        FOSDEM 2018's GlobalSign benchmark
        
        2018-10's Portavita's benchmark
  - - - https://www.pgcon.org/2016/schedule/attachments/414_queues-pgcon-2016.pdf
      - SKIP LOCKED
      - https://gist.github.com/chanks/7585810
- - - - Security
        
        Pyntch
        
        Spaghetti
        
        Requires
        
        Bandit
  - - - Lint
        
        shellcheck
- - - - Terraform
        
        Lint with terraform fmt -check
- - - - I Codebase: There should be exactly one codebase for a deployed service with the codebase being used for many deployments.
      - II Dependencies: All dependencies should be declared, with no implicit reliance on system tools or libraries.
      - III Config: Configuration that varies between deployments should be stored in the environment.
      - IV Backing services: All backing services are treated as attached resources and attached and detached by the execution environment.
      - V Build, release, run: The delivery pipeline should strictly consist of build, release, run.
      - VI Processes: Applications should be deployed as one or more stateless processes with persisted data stored on a backing service.
      - VII Port binding: Self-contained services should make themselves available to other services by specified ports.
      - VIII Concurrency: Concurrency is advocated by scaling individual processes.
      - IX Disposability: Fast startup and shutdown are advocated for a more robust and resilient system.
      - X Dev/Prod parity: All environments should be as similar as possible.
      - XI Logs: Applications should produce logs as event streams and leave the execution environment to aggregate.
      - XII Admin Processes: Any needed admin tasks should be kept in source control and packaged with the application.
- - - - markdownlint
- - - - Lightweight clusters
        
        kind
        
        k3s
        
        k3d
        
        minikube
        
        microk8s