> Any idea what kind of webservices? webmail? forums? different services >
will have different loads and so need more or less cpu's or disks. First stage of the project is some bespokish social networking application. With us being a nation without territory. we were trying to build around a sort of virtual nation theme. Clever marketing maybe. But more of a hook to build the sense of (abeit nationless) identity to the roma nation amongst the younger generation and entice more of them to become active in fighting to change the poor deal they get in life and to defend their unique culture. Why not facebook? Because it's far too easy to mine. With most living under regimes of institutionalised racism with government sponsered gangs of door to door racists. This is very sensitive data. And the whole setup needs to be locked down like a ducks ass after somebody bought a new welder. Also, the other big problem is language. AFAIK, the first language of most Roma have never been localised in any software ever. At least not on the internet or anywhere it counts. So, everything produced would need a unique set of localizations. A large number are totally illiterate. So ontop of people wanting to upload photo's (User videos some day in the future. But understand the technical challenges here would make this impractical for the forseeable future.) . Any informative content also needs to be available as either audio or video. The next stage involves once people are getting online and interacting introducing demographic elements. So there is a way of guaging what the people want on a large scale. And polling for opinions on various issues which affect directly. So, that the NGO organisations that represent the Roma on the world stage have access to actual representative information about what the people want and think. And such data would also provide a spotlight to show up the organisations which are using Roma as political bargaining chips rather than being helpful. And strengthen the ones that are doing it right. This project is not being undertaken by or the property of any organisation. It is intended to be run as an entirely politically and organisationally neutral entity of it's own. Only opening up polling and collating of data to pro-roma NGO's under a strict set of guidelines (that are still to be drawn up). And the project is being worked on by a small group of individuals of Roma heritage. Mainly old skool tribal eldery types, with the help of a few experts in the other relevant fields that this crosses over into. For some reason this appointments me as queen of all things tech, but ho hum :) So, don't need multi TB from the very start.... But room for storage redundancy and the initially tricky to guage initial growth without worrying /too much/ is where my mind at. The only tricky thing that is priority in my mind. Is the high level of user concurrency. Which is mainly RAM + a godly level of dead reckoning. I am considering architecting a few of the backend services as separate VM's on the iron from the start.... So that if it comes to expanding and breaking out into extra machines and devices in the future. Then it is an easy and straightforward task. There is a plan to be applying to places for grants once this gets underway... But the initial setup and launch is coming out of our own threadbare pockets. Yes, I realise how insanely ambitious this is. But where's the fun in life without insurmountable challenges?
> Any idea what kind of webservices? webmail? forums? different services >will have different loads and so need more or less cpu's or disks. First stage of the project is some bespokish social networking application. With us being a nation without territory. we were trying to build around a sort of virtual nation theme. Clever marketing maybe. But more of a hook to build the sense of (abeit nationless) identity to the roma nation amongst the younger generation and entice more of them to become active in fighting to change the poor deal they get in life and to defend their unique culture. Why not facebook? Because it's far too easy to mine. With most living under regimes of institutionalised racism with government sponsered gangs of door to door racists. This is very sensitive data. And the whole setup needs to be locked down like a ducks ass after somebody bought a new welder. Also, the other big problem is language. AFAIK, the first language of most Roma have never been localised in any software ever. At least not on the internet or anywhere it counts. So, everything produced would need a unique set of localizations. A large number are totally illiterate. So ontop of people wanting to upload photo's (User videos some day in the future. But understand the technical challenges here would make this impractical for the forseeable future.) . Any informative content also needs to be available as either audio or video. The next stage involves once people are getting online and interacting introducing demographic elements. So there is a way of guaging what the people want on a large scale. And polling for opinions on various issues which affect directly. So, that the NGO organisations that represent the Roma on the world stage have access to actual representative information about what the people want and think. And such data would also provide a spotlight to show up the organisations which are using Roma as political bargaining chips rather than being helpful. And strengthen the ones that are doing it right. This project is not being undertaken by or the property of any organisation. It is intended to be run as an entirely politically and organisationally neutral entity of it's own. Only opening up polling and collating of data to pro-roma NGO's under a strict set of guidelines (that are still to be drawn up). And the project is being worked on by a small group of individuals of Roma heritage. Mainly old skool tribal eldery types, with the help of a few experts in the other relevant fields that this crosses over into. For some reason this appointments me as queen of all things tech, but ho hum :) So, don't need multi TB from the very start.... But room for storage redundancy and the initially tricky to guage initial growth without worrying /too much/ is where my mind at. The only tricky thing that is priority in my mind. Is the high level of user concurrency. Which is mainly RAM + a godly level of dead reckoning. I am considering architecting a few of the backend services as separate VM's on the iron from the start.... So that if it comes to expanding and breaking out into extra machines and devices in the future. Then it is an easy and straightforward task. There is a plan to be applying to places for grants once this gets underway... But the initial setup and launch is coming out of our own threadbare pockets. Yes, I realise how insanely ambitious this is. But where's the fun in life without insurmountable challenges?
bandwidth first.
100K people needing to vote in a week. lets assume that half of them leave it till the last day.
50,000 in a day
lowball: 10 pages each for guestimate.
call it 200kb average per page with images and html etc.
Will people have to download documents? images? video? upload/download?
furthermore they're not going to be perfectly spread out over those 24 hours. most will be using it during a 6 ish hour slot when it's evening in europe.
so lets assume that you may need to handle 30K people voting in a 6 hour slot.
(2mb*30,000)/6
so call it 10GB per hour (lowball) or 3mb per second upstream, more if you don't want people to click and have to wait for 2 mins which is very much a buisness connection with a reasonable fraction of that downstream.
I can't guess how much CPU power you'd need without knowing how much you want to do for each user but at the moment I'm assuming you just want to let people log in,
read half dozen small pages or look at a few small images, vote then log out rather than view hundreds of large pages or images like facebook or submit and read lots of forum posts.
you'll need a database backend, probably on it's own server which can handle that kind of traffic though that depends largely on your implementation and database schema.
if reliability is important you'd need a duplicate web server and database server for failover in case of the server dying and prossibly more for other single points of failure.
you don't want to lose data so you'd need to budget for a decent commercial grade raid array and probably long term tape backup to be stored at a second site.
budget in some maintainance.
the software... the software could be fun depending on how complex this all is and could either be reasonably straightforward or a horrorshow to make reliable and secure. really secure isn't easy.
do you need it to be secure from kids or secure from governments or organisations with money? if the latter you'll have a tough time even with a very simple site with very few features.