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 icebraining on Wednesday April 11, 2018 @12:57AM (#16808160)

The question is whether it can be stored like this while allowing for fast queries. For example, unless it changed recently, Postgres doesn't calculate statistics to help the query planner on jsonb fields.

[ Parent | on HN ]

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

JSONB columns should behave just like any datatype with a GIN index in the recent releases, to my knowledge.

Still, a JSON column will arguably be faster than a pure KV table since you can more efficiently query it, especially any non-JSON columns.

[ Parent | on HN ]

Re:We saved $50k/year with a Go microservice coded in a hack... by ptman on Wednesday April 11, 2018 @05:08AM (#16809296)

IIRC JSONB still has problem with index statistics

So values in JSONB columns can be indexed nicely, but the statistics can be much worse than for non-JSONB columns, which can lead the query planner astray.

[ Parent | on HN ]

Re:We saved $50k/year with a Go microservice coded in a hack... by NickNameNick on Wednesday April 11, 2018 @05:42AM (#16809467)

Postgres will let you create an index on an expression into the JSON column, so querying should still be very quick.

[ Parent | on HN ]

Re:We saved $50k/year with a Go microservice coded in a hack... by matte_black on Wednesday April 11, 2018 @01:21AM (#16808273)

The answer would make a great blog post.

[ Parent | on HN ]