Why do we store the issue data in s3

Open
#126 1 comment 0 reactions 1 assignee View on GitHub

@RobStallion is already working on this.

Since Dec 4, 2018.

Assessment

This issue has not been assessed yet.

Description

discuss question technical

Why do we store our issue data as JSON in S3?

What are the pros/cons of storing this kind of data in S3 over our own sql database?
e.g.

  • is it faster to load data
  • is it cheaper
  • does it take up less space as a json file on S3 than as a string in postgres. If so could storing the data as a binary help? (see quotes below)

quotes from https://github.com/dwyl/phoenix-ecto-encryption-example

The reason we are creating the encrypted/hashed fields as :binary is that the data stored in them will be encrypted and :binary is the most efficient Ecto/SQL data type for storing encrypted data; storing it as a String would take up more bytes for the same data. i.e. wasteful without any benefit to security or performance.

The best data type for storing encrypted data is :binary (it uses half the "space" of a :string for the same ciphertext)

Dominant language
Elixir
Stars
33
Forks
3
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dwyl/github-backup

All issues in dwyl/github-backup

Similar issues

More Elixir issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.