Recent submissions

Comment · 8 months ago
This reminds me of my project a bit: https://www.scrydata.com/. I spent a bunch of time trying to automate the migration portion to take the risk out of doing these big migrations. I wonder if you thought a more automated tool might be of use for ongoing migration testing?
Comment · 8 months ago
We built a tool that catches migration regressions before production by replaying real query traffic against shadow databases.

The blog post walks through a concrete example: a missing index that causes a 92x regression on a core query path. Staging misses it because it has 100 rows instead of 25k. Scry catches it because it replays actual production queries at real data scale.

You can replay this exact scenario locally in under 2 minutes:

scry demo Install: https://github.com/scrydata/scry-cli/releases

The demo spins up a source Postgres, applies a migration with a missing index, replays captured traffic, and shows you the regression report. No cloud account needed — everything runs locally.

Happy to answer questions about the architecture (transparent PG proxy for query capture, CDC replication for shadow databases, NATS for event streaming).

Comment · 6 years ago
Comment · 13 years ago
Comment · 13 years ago
And the "What do we make of this" is definitely a valid question. Every model is going to be inaccurate to some degree. We should strive to improve them!

I took issue with picking a few individual researchers' models which have a lower range than the IPCC estimates (which are influenced by those lower estimates). The case could, and probably is, be made for higher ranged estimates. The point is, if you curate a subset of models to bolster your bias, you're not contributing any meaningful data to the discourse.

Comment · 13 years ago
I don't know that I agree with the thesis of this article whatsoever; basically some cherry-picked research estimates "we may only see 1.5 to 2 degree increases, and we haven't had any real warming in the past 10 years; Therefore, we might want to reevaluate the amount of energy and attention we spend on mitigating carbon emissions"

That seems like a pretty flimsy argument.

1. I don't think there's strong evidence that 'global average temperatures stopped increasing.' Many of the world's largest average temperature readings have happened in the last ten years (2010, especially, but even recent reports show upward trends: http://www.ncdc.noaa.gov/sotc/national/2012/13).

2. Cherry-picking a few people whose models show a lower than average range, doesn't tell me anything other than the author of this article is suffering from wishful thinking.

3. The heart of the article seems to be suggesting this: "If climate change isn't that bad, maybe we don't have to do anything about it, " but ignores the opposite proposition. Oddly, I'm not even sure why such an article is necessary since the world collectively isn't making any earnest attempts to curb carbon emissions. Any reductions have been economically based, not environmental.

No, I think this is a hit piece on the climate change movement couched as due-diligence and beneficial skepticism.

Comment · 14 years ago
This may be old, but I just stumbled upon it.
Comment · 15 years ago
I'm not sure you read the article fully, because relationships were never described in the article. Instead, it was high read/update load which caused problems.

Mongo, on paper, should be an ideal candidate for this job; but, due to complications with the locking model and with its inability to do online compactions, it's failing.

Comment · 15 years ago
I'm more interested in which databases people are using.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton