Personally I'd go with JSON files and some random JSON library for writing, cache and reading stuff.
I would ask you to go back to /g/ or whatever you came from, because you are exactly the kind of person that went with XML files and some random XML library for writing, cache and reading stuff 5 years ago.
>>3
That. I would also use the Spring framework to implement the scalable enterprise n-tier turkey anonymous inversion of control web forum solution.
Name:
Anonymous2012-12-27 5:16
Don't need a persistent database at all. Just use JSON with redis. Think about it, image boards prune content very rapidly so there's little use for a database. Archive 404'd threads as serialized JSON or plain HTML.
Name:
Anonymous2012-12-27 5:20
who gives a fuck what data storage layout you people would hypothetically use?
>>5
According to the front page there's 92GB of content in total for all of the boards.
If they split the boards across different servers they could hold everything in memory and not bother with persistent storage at all.
In that case, just store all the HTML pages and images in a huge in-memory hashtable.
128GB of DDR3 can be had for <$1000.
Name:
Anonymous2012-12-27 6:11
Personally I'd go with JSON files
Too much work. I'd just use Postgre SQL reliable and fast enough solution with minimum work. Who the fuck wanted to do anything extra in web development hell?
Name:
Anonymous2012-12-27 6:12
lel i would use fioc and redis and would have upvote/downvote buttons
>>13
Yes, your solution is simpler is starting from nothing. But I would use some bloated framework, like RoR or Django, and write maybe ten lines of code and be done with it. Those frameworks work with real databases. With files, you'd had to do some basic functionality yourself.
Though, files are not that bad choice for 4chan kind of simple site. But I'm just too lazy to do it that way.
>>1,9
You people choosing between JSON and Postgresql look like kids who decide what to use to build a rocket to fly to Mars: cardboard or modelling clay.
holding all ones shit in memory will do (this hi-tech hi-load technique is called ``redis'' nowadays). but i believe that content pruning was introduced because of technical feebleness.
i'll go with riak.
Name:
Anonymous2012-12-27 14:47
>>20
So you don't have to buy 128GB of RAM. And there's no penalty in serving static files from the file system.