4 ms·
PartiQL on DynamoDB is just syntactic sugar. DynamoDB is not meant to be used that way, but it's query and insert language can be a bit tricky, PartiQL just a h
by CSDude 4y ago
PartiQL on DynamoDB is just syntactic sugar. DynamoDB is not meant to be used that way, but it's query and insert language can be a bit tricky, PartiQL just a helper for that weird query syntax, you can't do joins or aggregates. PartiQL is supported by QLDB, Redshift as well, to unify a querying language somewhat. Docs should be much more clearer to indicate the dangers of it , to avoid confusion like this.
But you can scan MongoDB, Elastic with Presto in parallel it works great when you need to run it, a few times. But if you find yourself using a NoSQL data store as relational, or OLTP cases just because you have ability to run SQL on it is going to hurt you and it should be obvious. As with everything in software, it depends.
We use PartiQL library directly at Resmo https://www.resmo.com https://www.resmo.com because it makes querying the datastore with nested values easier and the its storage independent.
- deleted 4y ago[deleted]
- chris_armstrong 4y agoI think treating PartiQL as syntactic sugar is the mature approach - no one is under any delusions then as to how the database works. I mostly use it for ad hoc stuff whenever I need to get at something quickly. The SDK interface is horrible in its own right.
- jugg1es 4y agoYea, I always thought of PartiQL as a replacement for the overly-complicated DynamoDB SDK (it has 2 different 'versions' and multiple query modes - a low level API and a higher document level).