News for hackers. Stuff that matters.

A comment on JrGQL, a GraphQL alternative. Parent comment

Re:JrGQL, a GraphQL alternative by daurnimator on Monday August 14, 2017 @02:57AM (#15006997)
The most valuble thing IMO is being able to perform all data fetches in the one database transaction; this means that you get consistent data inside of your application (rather than different divs being out of sync if the page loads while the server is updating content)
[ Parent | on HN ]
Re:JrGQL, a GraphQL alternative by alvis on Monday August 14, 2017 @03:26AM (#15007097)
This is likely untrue. Unless you fetch data only from one single database, so that you can perform an atomic transition, GraphQL cannot guarantee you to receive the data you want. Technically, a GraphQL server may combine data into a single return from different sources where locking is not possible.
[ Parent | on HN ]
Re:JrGQL, a GraphQL alternative by daurnimator on Monday August 14, 2017 @04:06AM (#15007211)
> This is likely untrue. Unless you fetch data only from one single database, so that you can perform an atomic transition

I do! I find it odd that anyone would do anything else...

[ Parent | on HN ]
Re:JrGQL, a GraphQL alternative by KirinDave on Wednesday August 16, 2017 @03:49PM (#15030636)
It is a lovely world when you can do this.

In microservices-driven-architrctures you often have to appeal to multiple services to service a request.

[ Parent | on HN ]