What are some good, fast persistent storage options for key->value data? [closed]

S

7

17

For a small PHP app I am writing, we need to store a large number of records that have a hash key, and a few simple field values ('host', 'path'). eg:

'4420ffb32a' => array(
  'host' => '127.0.0.1',
  'path' => 'path/to/resource',
);

What is the best persistent storage for data like this? Would MySQL be the best choice, or is it overkill for such simple data? What would give the best performance?

Saval answered 19/10, 2010 at 20:16 Comment(0)

C

13

Short answer: Membase.

Long answer:
You basically have three options: a relational database, file storage, or something else.

Like you said, a relational database could definitely be overkill. That said, if this is part of an application that already has a MySQL or other database, I would go with that. Likewise, file storage can be handy sometimes (writing to a bunch of XML files, for example), but disk I/O can be slow.

Now in the other category, you have some great NoSQL options like CouchDB or Memcached.

If you aren't too worried about the persistence of your data, I'd recommend memcache. It's lightweight, easy to get running, and there is a Memcache PHP extension that makes using it easy. It is made for key-value storage like this.

The one drawback memcache has is that all your data is lost the second the memcache service stops. This is where Membase comes in. It is an open-source fork of memcache that is protocol-compatible, meaning it will work with all existing client libraries. However, it can persist your data and actually provide consistency and reliability, something memcache can't on its own.

NOTE: This answer is a relic of its time, as is the question itself. Please do not take it literally.

Colson answered 19/10, 2010 at 20:30 Comment(2)

The long answer is appreciated. I'm reviewing membase now. – Saval 19/10, 2010 at 20:39

Or use MySQL with Memcached: dev.mysql.com/tech-resources/articles/… – Stuffing 23/11, 2011 at 9:20

C

5

Just to suggest something different, redis (or redisdb-win32 if you're on a Windows servers)

Capel answered 19/10, 2010 at 20:30 Comment(1)

Interesting suggestion - I hadn't looked at redis before... – Saval 19/10, 2010 at 20:31

C

4

CouchDB is your answer (although it could be a little bit overkill for your necessities)..

Catherincatherina answered 19/10, 2010 at 20:19 Comment(0)

V

2

Strange no one mentioned Flintstone till now.

Also a good option is Doctrine.

Vertebra answered 21/10, 2015 at 20:39 Comment(2)

The quetion is about 1 exact storage, not ORM that uses multiple storages – Footrest 24/1, 2017 at 15:18

@Basil Musa, thanks a lot! The Flintstone was actually what I was looking for!! a simple file-based stogage =) serialized – Phallic 17/4, 2019 at 22:40

S

1

Might not be the best answer. But I would store it into a mySQL Database and probably use a mysql_pconnect if the data are not being extracted at the same time.

Informations about pconnect here: php.net

A common alternative to Database is a plain file but correct me if I'm wrong but concurent file access might be slower.

Good luck.

Soft answered 19/10, 2010 at 20:21 Comment(0)

C

1

To add some more to those already mentioned, PHP has native support for

For the latter there is a nice article by Johannes Schlüter.

Confraternity answered 19/10, 2010 at 21:18 Comment(0)

M

0

i would go for MySQl, just in case you need to upgrade your application in the future. Better be future proof when it comes to applications.

Marchellemarcher answered 20/10, 2010 at 7:23 Comment(0)

Recommended topics

Hot tags