Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

Writing a DB

Name: Anonymous 2010-05-16 5:44

Objective: write fast and simple database program. Interaction with external applications through socket.
What's the best way to organise memory usage and file storage? I've come up with reading file and decomposing it into array elements. But there can be problems as file size limit and memory usage restrictions.
Any ideas?

Name: Anonymous 2010-05-16 5:47

Are you planning on storing such massive amounts of data? Do you want to distribute it across servers? You'll have to be more specific.

Name: Anonymous 2010-05-16 5:51

>>2
Possibly. Yes.

Name: Anonymous 2010-05-16 5:52

I recommend scalable enterprise NoSQL solutions.

Name: Anonymous 2010-05-16 10:42

Name: Anonymous 2010-05-16 11:09

If the point is to write it yourself, NoSQL will be much easier to implement than anything else, simply because it barely does anything.
If the point is to have a working database, use Postgres.

Name: Anonymous 2010-05-16 21:10

>>6
anon is wise

Name: Anonymous 2011-02-02 22:47

Name: Anonymous 2011-02-04 19:29

<

Don't change these.
Name: Email:
Entire Thread Thread List