Topics /

Databases & Data

The most popular blog posts about databases & data on Hacker News. 4,222 posts.

Any year
1443

New storage classes for Google Cloud Storage

Businesses seek the best price and performance to suit the storage needs of workloads ranging from multimedia serving, to data analytics and machine learning, to data backup/archiving, all of which drive demand for a variety of storage options. At Google, we aim to build a powerful cloud platform that can meet the…

1453

SQL nulls are weird

Yes, you read that right. SQL does treat all NULLs as distinct values. I learnt this a while back while working on Convoy and again on LiteQueue: a Golang a queueing library. Basically, any column wi

1456

Asynchronous Python and Databases

To quote the last part of this blog post, "I think it's [asyncio] really well done, it's fun to use, and I still am interested in having more of a SQLAlchemy story for it, because I'm sure folks will still want this no matter what anyone says.". To that end, SQLAlchemy 1.4 now includes complete support for asyncio …

1466

A Tale of Query Optimization

Last December, I got an interesting bug report from the VWO support team. It seemed like the loading time of a particular analytics report was ridiculously slow for a big Enterprise customer. Since I am part of the Data platform, a flag was immediately raised and I got involved in debugging the issue.

1467

DuckDB-Wasm: Efficient analytical SQL in the browser

DuckDB-Wasm is an in-process analytical SQL database for the browser. It is powered by WebAssembly, speaks Arrow fluently, reads Parquet, CSV, and JSON files backed by Filesystem APIs or HTTP requests, and has been tested with Chrome, Firefox, Safari, and Node.js. You can try it at shell.duckdb.org or on Observable.

1470

Optimizing Ruby's JSON, Part 4

In the previous post, we established that as long as ruby/json wasn’t competitive on micro-benchmarks, public perception wouldn’t change. Since what made ruby/json appear so bad on micro-benchmarks was its setup cost, we had to find ways to reduce it further.