We saved $50k/year with a Go microservice coded in a hackathon

Re:We saved $50k/year with a Go microservice coded in a hack... by EGreg on Wednesday April 11, 2018 @10:03AM (#16811147)

Here is the thing - encrypted stuff is just a weird encoded string. So I can’t really use columns normally.

What I really need is just a huge table with two fields: “token”, “content”

And the token is basically the primary key but encrypted with whatever encryption.

You could even do foreign keys this way.

Hmm I suddenly have an idea. What about a layer above the database that basically enforces foreign keys and joins in this way to support end to end encryption? The content would reference ENCRYPTED foreign keys. Only clients would decrypt stuff.

[ Parent | on HN ]

Re:We saved $50k/year with a Go microservice coded in a hack... by pandapunchpower on Wednesday April 11, 2018 @10:40PM (#16817573)

>What I really need is just a huge table with two fields: “token”, “content”

Sounds more like a key value store and less like a relational database. Although you can store key value data in a relational db of course, there may be a better tool for the job.

[ Parent | on HN ]

Re:We saved $50k/year with a Go microservice coded in a hack... by JoachimSchipper on Thursday April 12, 2018 @02:00PM (#16823331)

You'll be interested in CryptDB.

[ Parent | on HN ]