I would like to use Anahita to build a social network in my iPhone app. Do you know how it scales with the network size ? Does it depends on the server too ?
We are building for high scalability, but at this moment I don't have any examples to provide you, because many Anahita projects are still in the infancy stage and haven't reached the critical mass. The best we can do at this moment to take software design approaches that we know will lead to better performance and most flexible architecture.
As our user base grow and more data becomes available, we can also look into the common bottle necks and improve performance and flexibility of the system. Having said that, every social network will also have it's own unique bottlenecks and performance challenges that require unique solutions. Those scenarios have to happen first, so we can identify them and provide solutions.
Does it depends on the server too ?
Of course! A lot of has to do with the server and database power and configuration.
This year we will be investing more time on mobile accessibility. As you know we have a startup project called http://www.TinyRecipe.com which will be a mobile social networking service for sharing food recipes. As we grow that project all the aquired knowledge will be shared with the Anaha tribes.
Try not to think about scalability in the beginning, is a problem i see many people obsessed for, but to me is a non-problem. Build it, get traction and if it will grow that much that you need to figure out scaling issues you will have the resources for it. Otherwise is like focusing on buildind a multiple storey buidling car park to fit into it just a bycicle.
Anahita is built using php, and mysql as FB is, so it can be scaled to few hundred milion users, but first you need to get there :)
Hi Barbara,
We are building for high scalability, but at this moment I don't have any examples to provide you, because many Anahita projects are still in the infancy stage and haven't reached the critical mass. The best we can do at this moment to take software design approaches that we know will lead to better performance and most flexible architecture.
As our user base grow and more data becomes available, we can also look into the common bottle necks and improve performance and flexibility of the system. Having said that, every social network will also have it's own unique bottlenecks and performance challenges that require unique solutions. Those scenarios have to happen first, so we can identify them and provide solutions.
Of course! A lot of has to do with the server and database power and configuration.
This year we will be investing more time on mobile accessibility. As you know we have a startup project called http://www.TinyRecipe.com which will be a mobile social networking service for sharing food recipes. As we grow that project all the aquired knowledge will be shared with the Anaha tribes.
Try not to think about scalability in the beginning, is a problem i see many people obsessed for, but to me is a non-problem. Build it, get traction and if it will grow that much that you need to figure out scaling issues you will have the resources for it. Otherwise is like focusing on buildind a multiple storey buidling car park to fit into it just a bycicle.
Anahita is built using php, and mysql as FB is, so it can be scaled to few hundred milion users, but first you need to get there :)
Thanks guys for your precious answers. It helps a lot!
You must be logged in to comment!