3 ms·
It's PostgreSQL, so we can and do query the JSON data, and update deepely nested fields in the JSON natively as well (no need to take a lock, read the entire bl
by zegl 4y ago
It's PostgreSQL, so we can and do query the JSON data, and update deepely nested fields in the JSON natively as well (no need to take a lock, read the entire blob, modify it in the application, save the data, and release the lock).
PostgreSQL supports setting values, appending to arrays, etc etc natively in an ACID compliant way.
- paavohtl 4y ago> so we can and do query the JSON data Also supported in DynamoDB - it's a JSON-database after all. > update deepely nested fields in the JSON natively as well https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.UpdateExpressions.html https://docs.aws.amazon.com/amazondynamodb/latest/developerg... > PostgreSQL supports setting values, appending to arrays, etc etc natively in an ACID compliant way. https://aws.amazon.com/blogs/aws/new-amazon-dynamodb-transactions/ https://aws.amazon.com/blogs/aws/new-amazon-dynamodb-transac... I'm not saying PostgreSQL is a bad choice by any means, or that DynamoDB is suitable for all projects. But good support for JSON is in no way a capability unique to PostgreSQL. At least ideally, a competently built document database should be at least as good if not better than an SQL database emulating a document database.
- platz 4y agoDynamoDB doesn't let you store JSON natively. You have to translate that json into dynamodb keys and attributes.
- deleted 4y ago[deleted]