Live data from Hacker News

Launch HN: Ardent (YC P26) – Postgres sandboxes in seconds with zero migration

tryardent.com

51–60 of 61 posts

Re: Launch HN: Ardent (YC P26) – Postgres sandboxes in seconds with zero migration

#51

Does it clone the data? We have a table with 35GB data, what happen in that case?

It does clone the data. It uses copy on write to clone so data size won't slow it down since it's a metadata operation instead of actual data movement

It clones the entire DB so it's not quite 6s per TB but actually the entire thing takes Probably something to adjust on the site to make it clearer!

Re: Launch HN: Ardent (YC P26) – Postgres sandboxes in seconds with zero migration

#52

Congrats on the launch! One note on the pricing: it would kind of bum me out to pay $250/month for $100/month in credit. That feels like I'm losing $150/month.

Totally makes sense. We do offer a pure PAYG tier (starter) that scales completely dynamically to workload

But seems like this may be less about the absolute price but more about the way the 100/month of credit feels?

What do you think could be better? The intention of the 250/month scale tier was intended for companies scaling up that want BYOC for data residency etc. etc. and give them enough to test things internally without worrying about an overage bill before running it directly on prod but this might be able to be implemented better.

Re: Launch HN: Ardent (YC P26) – Postgres sandboxes in seconds with zero migration

#53

Congrats on the launch! DB clones have been a game changer for my team, allowing us to build isolated workspaces for agents to do work ranging from optimizing queries/views to building UI/UX that works for the actually combinations of data we have. We self-host DBLab since we had trouble getting Xata, Neon, and hosted DBLab configured.

Hey, PostgresAI founder here.

thank you for using DBLab

Can you DM me, please? Really curious about your experience

Re: Launch HN: Ardent (YC P26) – Postgres sandboxes in seconds with zero migration

#55

Earlier quoted context omitted.

I wanted to try doing something similar to this in our dev environment (think shared dev database but per branch clones), but this limitation seemed tricky to accept: > The source database can't have any active connections during cloning. I wouldn't mind some lock contention, but having to kill all connections seemed a bit harsh

I guess it's still possible with a replica that no one is using? So you don't need to touch real production db? Not sure if it applies for all use cases tou

Yeah I think a read replica might fit the bill - though I suspect active logical replication counts as a connection in this context.

Using a cloud provider read replica might not (as I think that might use block level replication) - but then you're paying for an extra dev database host for the privilege

Re: Launch HN: Ardent (YC P26) – Postgres sandboxes in seconds with zero migration

#57

Earlier quoted context omitted.

If it’s production data I probably don’t trust a random startup with it. I’m very confused as to the target market here

I’ll bite. You’re a dev at random mid size company and tasked with using this newfangled agentic tech to implement an intranet feature everybody wants and nobody else wants to build. How do you get a staging and dev db together that’s going to let you test your migrations?

Spin it up my self inside our VPC ?

I can only imagine this being fine for 1 person side projects.

Re: Launch HN: Ardent (YC P26) – Postgres sandboxes in seconds with zero migration

#58
post #36
post #34

Earlier quoted context omitted.

A little slow but on Aurora you can attach then promote read replicas. Iirc that's around 20 minutes but I haven't tested recently. I'd think you could also setup logical rep to a VM then snapshot and clone the storage which is generally pretty fast.

You can create a new instance directly on AWS aurora. Takes less than 20 minutes! aws rds restore-db-cluster-to-point-in-time \ --source-db-cluster-identifier \ --db-cluster-identifier \ --restore-type copy-on-write \ --use-latest-restorable-time \ --db-subnet-group-name \ --vpc-security-group-ids \ --serverless-v2-scaling-configuration MinCapacity=0,MaxCapacity=16

Any idea on timing? I was under the impression pretty much anything RDS takes ~20 minutes although I haven't done any benchmarking/timing on the latest Aurora stuff

Main exceptions are copying/encrypting snapshots when they're not incremental and PITR restores which can take substantially longer.

Re: Launch HN: Ardent (YC P26) – Postgres sandboxes in seconds with zero migration

#59
post #41
post #30

Earlier quoted context omitted.

There's no reason why it shouldn't, Delphix primarily targeted Oracle, but there is of course not as much open-source enthusiasm for supporting a proprietary database as an open-source one.

And also, of course, MS-SQL is only supported on Windows, and ZFS is not available on Windows. Windows does have Volume Shadow copy Services, but they are not as capable as ZFS snapshots and clones.

MS SQL has been available on Linux for around 10 years now.

So is the magic basically to use ZFS and everything should work fine?

Post reply on HN