HN user

jfbaro

112 karma
Posts0
Comments72
View on HN
No posts found.

coW? So devs can have their ephemeral databases in seconds at no cost? Only the reads and writes they use and the “delta” storage of their thin clone?

Bitenporal support?

Smart anonymization (like Tonic.AI)?

Looking forward to hearing the announcements

GPT-4 3 years ago

Even if a GTP-X will be able to get my description of a system and because it understands the industry lingo and practices create a extremely optimized RUST code, why would we need systems like apps and webapps (like internet bankings) in a world where we all have access to GTP-X?

Like program a KUKA robot to manufacture typewriters in 2023.

How "computer systems" will look like?

Great list. As I can add anything here, I will say:

- Bitemporal support OOTB (storage would be more expensive, as temporal data needs more disk space)

- CoW capabilities OOTB, so it would be super easy (fast and cheap) to create ephemeral database for development purpose.

- Charge per request (ms of reads, ms of writes) - for the sake of being more specific about serverless.

- AI capabilities that detects the use of the database and suggests indexes or other tweaks to make the database as fast as possible (and cheap), even if schema changes, database size increases or query patterns change

- PostgreSQL support (and all its extensions... I know that's a hard one as PS is based on MySQL)

- OOTB capabilities for Masking and/or anonymizing of data (PCI, PII, etc)

Thanks

Great work Amazon Web Services (AWS)! I am already waiting for V3.... Wish list:

- Pay per transaction (Reads, Writes) + Storage, instead of per resource allocation (some competitors are offering this already).

- No need for VPC, just like DynamoDB does today.

- Multi-region sync replication (no data loss in case a region goes down), but on a per-table base.

- Self-tuning capabilities, like ottertune and postgres.ai

- Unlimited Fast Database Cloning copies for non-production environments (COW)

- Transparent connection pooler (useful when using Lambda)

That's amazing! Thanks for making this open source.

Could this be extended to support temporal (and Bitemporal) tables? Some storage level optimizations could benefit performance and easy of use for use cases temporarily is important, like financial services systems.

Thanks

First and most important thing: Congrats to the Cloud Functions team for moving GCF forward.

Second: Please, keep working on reducing the cold start times, min-instance is useful, but it is kind of a hack IMHO.

Third: Native support for RUST would be amazing.

Wow, is there any public list or documentation about these common cases and how to make them faster in PG? I would expect the PG query optimizer to fix this automatically, but as it doesn't, having this documentation would be of great use for many developers. Thanks for sharing!