Simon Willison’s Weblog

Subscribe
Atom feed for databases

102 items tagged “databases”

2008

Spock Proxy. A MySQL Proxy fork (no Lua) that concentrates solely on sharding, by parsing incoming SQL statements and redirecting them across multiple databases. There are some limitations on the SQL that can be handled (no nested queries, joins across a maximum of two tables) but generally it looks pretty impressive.

# 11th December 2008, 9:49 am / spockproxy, mysql, sharding, databases, scaling

A Brief Tour of Graphd. The secret sauce behind Freebase—a custom written graph server that models everything as a typed, versioned relationship and can churn through over 3,000 simple queries a second on a single AMD64 core.

# 29th September 2008, 11:32 am / freebase, grahd, graphserver, databases

Hugely informative thread on multi-db support in Django. I brain-dumped some ideas for a Django multi-database connection API on the developer list, and got a ton of smart push-back from people who’ve been there and have the scars to prove it.

# 10th September 2008, 11:31 pm / multidb, django, databases

Drizzle, Clouds, “What If?”. Exciting news in the world of MySQL: Drizzle is a new project to produce a massively stripped down version of the database server—InnoDB/UTF8 only, no permissions, views, stored procedures or triggers, simplified field types, optimised for the common subset of functionality used by web apps. MySQL’s Firefox?

# 23rd July 2008, 12:30 am / mysql, databases, innodb, utf8, drizzle

Historically the project policy has been to avoid putting replication into core PostgreSQL, so as to leave room for development of competing solutions [...] However, it is becoming clear that this policy is hindering acceptance of PostgreSQL to too great an extent, compared to the benefit it offers to the add-on replication projects. Users who might consider PostgreSQL are choosing other database systems because our existing replication options are too complex to install and use for simple cases.

Tom Lane

# 7th July 2008, 2:08 pm / replication, postgresql, tom-lane, databases

Sun To Acquire MySQL. Sun also employ Josh Berkus, one of the lead developers of PostgreSQL.

# 16th January 2008, 1:55 pm / mysql, postgresql, sunmicrosystems, sun, tim-oreilly, databases, open-source, josh-berkus

2007

What You Need To Know About Amazon SimpleDB. Amazon have finally launched the database component of their web service suite. It fits a bunch of current trends: key/value pairs, schemaless, built on top of Erlang. “Eventual consistency” is an interesting characteristic.

# 14th December 2007, 11:21 am / amazon, simpledb, web-services, schemaless, erlang, hashtables, scaling, databases, charles-ying

PostgreSQL 8.3 beta 4 release notes. In addition to the huge speed improvements, 8.3 adds support for XML, UUID and ENUM data types and brings full text (tsearch2) in to the core database engine.

# 12th December 2007, 12:43 am / tsearch2, postgresql, xml, uuid, enum, databases, beta, full-text-search

Django Evolution. Really smart take on the problem of updating database tables to reflect changes to Django models. Code that automatically modifies your database tables can be pretty scary, but Evolution seems to hit the right balance.

# 23rd November 2007, 11:49 pm / djangoevolution, django, orm, databases, schema, migration

CouchDB “Joins”. Different approaches to indexing a blog post and its associated comments in the non-relational CouchDB.

# 25th October 2007, 8:27 am / erlang, databases, christopher-lenz, couchdb, joins, relational, views

CouchDB: Thinking beyond the RDBMS. CouchDB is a fascinating project—an Erlang powered non-relational database with a JSON API that lets you define “views” (really computed tables) based on JavaScript functions that execute using map/reduce. Damien Katz, the main developer currently works for MySQL and used to work on Lotus Notes.

# 3rd September 2007, 9:48 am / couchdb, erlang, databases, json, javascript, damien-katz, lotusnotes, mysql, mapreduce

SELECT * FROM everything, or why databases are awesome. I’m beginning to think that for scalable applications the thinner your ORM is the better—if you even use one at all.

# 22nd June 2007, 12:40 am / rails, orm, blaine-cook, scaling, twitter, databases, sql