Date: Wed, 12 Dec 2018 23:37:00 +0100
From: Nicolas Paris <nicolas.paris@riseup.net>
To: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL VS MongoDB: a use case comparison
Message-ID: <20181212223435.6ztr43afpmxngk3g@riseup.net>
Mail-Followup-To: pgsql-performance@postgresql.org
References: <d43fd220-09f7-af4c-2623-44f094b15115@portavita.eu>
 <20181119172609.GR3415@tamriel.snowman.net>
 <d6f5de69-548a-d155-f0d7-f27233569600@portavita.eu>
 <20181120133420.GA3415@tamriel.snowman.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20181120133420.GA3415@tamriel.snowman.net>
Priority: normal
Precedence: bulk

On Tue, Nov 20, 2018 at 08:34:20AM -0500, Stephen Frost wrote:
> > Anyway, to bring data from JSON to a relational model is out of topic
> > for the current discussion, since we are actually questioning if
> > Postgres is a good replacement for Mongo when handling JSON data.
> 
> This narrow viewpoint isn't really sensible though- what you should be
> thinking about is what's appropriate for your *data*.  JSON is just a
> data format, and while it's alright as a system inter-exchange format,
> it's rather terrible as a storage format.

I would add that *FHIR* is an inter-exchange format instead of a storage
format. FHIR spec evolves and its json format too. When implemented in
a relational format it allows to only change the serialization process
(eg: json_tuple & co) instead of the data. In case FHIR is stored as a
json, it makes the information frozen in its version and complicate to
make evolve.


-- 
nicolas