SQL server vs. document store

105 views
Skip to first unread message

Roy van Pelt

unread,
Apr 6, 2016, 8:34:02 AM4/6/16
to FHIRbase
Hi all,

Looking into FhirBase, and it seems a neat and promising solution. Just curious: how does this compare to a document store? With all the jsonb types it kind of resembles document store functionality right?

Can anyone shed some light on this?

Thanks!

Roy

Николай Рыжиков

unread,
Apr 6, 2016, 1:00:37 PM4/6/16
to Roy van Pelt, FHIRbase

The key point to take  best of two worlds: ACID of RDBMS , expressiveness of SQL and  advantages of postgresql indexes with flexibility of schema-free document.

Jsonb matches FHIR resources and api, but leaves you ability to do complex searches and analysis using SQL.

Also maturity of postgresql  is not the last argument.

73's nicola

--
You received this message because you are subscribed to the Google Groups "FHIRbase" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fhirbase+u...@googlegroups.com.
To post to this group, send email to fhir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fhirbase/04ae0a7a-1834-4344-ad3a-739b3a464600%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

sarvy...@gmail.com

unread,
Jun 28, 2019, 8:27:05 AM6/28/19
to FHIRbase
I am unable to understand how it is adhering to ACID properties when we are dealing with only JSON structure. Can you provide some link or example where it can show ACID test on fhirbase.


On Wednesday, April 6, 2016 at 10:30:37 PM UTC+5:30, Николай Рыжиков wrote:

The key point to take  best of two worlds: ACID of RDBMS , expressiveness of SQL and  advantages of postgresql indexes with flexibility of schema-free document.

Jsonb matches FHIR resources and api, but leaves you ability to do complex searches and analysis using SQL.

Also maturity of postgresql  is not the last argument.

73's nicola

On Apr 6, 2016 3:34 PM, "Roy van Pelt" <royva...@gmail.com> wrote:
Hi all,

Looking into FhirBase, and it seems a neat and promising solution. Just curious: how does this compare to a document store? With all the jsonb types it kind of resembles document store functionality right?

Can anyone shed some light on this?

Thanks!

Roy

--
You received this message because you are subscribed to the Google Groups "FHIRbase" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fhir...@googlegroups.com.

Николай Рыжиков

unread,
Jun 28, 2019, 8:40:19 AM6/28/19
to sarvy...@gmail.com, FHIRbase
Hi, in postgresql you all oparations (doesn't  matter jsonb or not) are transactional, for example batch update like this:

update patient ser resource = resource  || jsonb_build_object('active',true); 

this statement will add new element to all , let say millions,  patients. This operation  will be acid, ie if it would fail or canceled,  no data will be updated, other queries do not see changes until this transaction is committed  etc.

With mongodb, you do not have same guarantees and you have to check data consistency manually  from your app.






пт, 28 июн. 2019 г., 15:27 <sarvy...@gmail.com>:
To unsubscribe from this group and stop receiving emails from it, send an email to fhirbase+u...@googlegroups.com.

To post to this group, send email to fhir...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages