91–100 of 146 posts
Earlier quoted context omitted.
It's Postgres compatible, so not exactly non-portable
Cough, not exactly: https://docs.aws.amazon.com/aurora-dsql/latest/userguide/wor...
Earlier quoted context omitted.
"like this" meaning you want wire PG compatibility, so you'd do something like this? UPDATE kv SET value = 'alpha' WHERE key = 'beta.charlie'; UPDATE s3 SET value = $b64$good luck$b64$ WHERE key = '/some/s3/path'; LISTEN whatever;
I don't know what I want exactly but I'm thinking along the lines that SQL is already doing a lot so it would make the most sense to start with a database interface and augment from there, to try to build a system to handle all the common forms of durable storage used by applications. The type of situation I'm thinking about is for example storing a blob in S3, storing metadata and a reference to the blob's path in a…
https://github.com/turbot/steampipe#steampipe-plugins and https://steampipe.io/docs/steampipe_postgres/overview may be relevant, although watch out for Steampipe's license
https://github.com/topics/foreign-data-wrapper and https://github.com/topics/fdw are some other examples
1: https://www.postgresql.org/docs/17/fdwhandler.html (although strictly speaking that page is for _authoring_ FDW, not a tl;dr of the concept)
I find it to be super limited, and I'm sort of struggling to see the point given all these constraints. No temporary tables, no foreign keys, no views, no more than 10k rows in a transaction. Except for some basic wire compatibility with the postgres protocol, I'd hardly call this a "database", and more a key-value store. https://docs.aws.amazon.com/aurora-dsql/latest/userguide/wor...
AWS tends to prioritize performance and scalability over functionality, which is reflected in the design of DynamoDB, SimpleDB, and now DSQL. I'm also not a big fan of this style. It doesn't give customers the flexibility to choose their own trade-offs like Spanner does and assumes that customers can't make these kinds of decisions on their own.
Just tried a quick test cluster - Identifies as PG 16.5 No views/triggers/sequences No foreign key constraints No extensions No NOTIFY ("ERROR: Function pg_notify not supported") No nested transactions No json(b) Unsupported PG features are now online https://docs.aws.amazon.com/aurora-dsql/latest/userguide/wor...
I also now don’t get why they are emphasizing PostgreSQL here when they should be emphasizing CQL compatibility. Being compatible with Postgres wire protocol but not being relational is strange.
Just tried a quick test cluster - Identifies as PG 16.5 No views/triggers/sequences No foreign key constraints No extensions No NOTIFY ("ERROR: Function pg_notify not supported") No nested transactions No json(b) Unsupported PG features are now online https://docs.aws.amazon.com/aurora-dsql/latest/userguide/wor...
https://docs.aws.amazon.com/aurora-dsql/latest/userguide/CHA... The quotas page is always the most interesting for any aws service. 10Mb transaction size and 5min transaction duration limits are interesting limitations that kill any "everything lives in the db" notions that one might have. A fully transactional, scalable, distributed data store + queue + db + data stream with triggers is my endgame Also, the 128mb li…
Just tried a quick test cluster - Identifies as PG 16.5 No views/triggers/sequences No foreign key constraints No extensions No NOTIFY ("ERROR: Function pg_notify not supported") No nested transactions No json(b) Unsupported PG features are now online https://docs.aws.amazon.com/aurora-dsql/latest/userguide/wor...
> No foreign key constraints Wat?
Earlier quoted context omitted.
https://docs.aws.amazon.com/aurora-dsql/latest/userguide/CHA... The quotas page is always the most interesting for any aws service. 10Mb transaction size and 5min transaction duration limits are interesting limitations that kill any "everything lives in the db" notions that one might have. A fully transactional, scalable, distributed data store + queue + db + data stream with triggers is my endgame Also, the 128mb li…
Do you really need transaction on analytic queries though? What are the use case for such transactions
Oof, press release proof readers must have been hit by layoffs > With its innovative active-active distributed architecture, Aurora DSQL is designed for 99.99% availability in single-Region configuration and 99.999% in multi-Region configuration, with an innovative active-active, distributed architecture, making it ideal for building highly-available applications We get that its architecture is innovative and active-…